Tuning up...
Security remediation

Security holes,
patched and proven closed.

Website and app security remediation from Chiang Mai, for companies in Thailand and abroad. We audit what you run — PHP and WordPress, Laravel, Node.js, Next.js, React Native, iOS and Android — patch what is exploitable within days, check whether anyone got in first, and harden the stack so the next advisory is a non-event.

Scope

What a remediation
covers.

♪

Websites and web apps

WordPress and its plugins, Laravel, Drupal, Magento, Next.js, Astro, Rails, Node.js and Express, with the servers they run on: nginx, Apache, PHP-FPM, Docker, Linux.

♫

Mobile apps and APIs

React Native and Expo, native iOS and Android, the SDKs and the backend APIs behind them: authentication, token handling, storage, update pipelines and store builds.

♬

Dependencies and supply chain

npm, Composer and PyPI packages, GitHub Actions and CI secrets, container images and the credentials scattered through .env files. We find what is exposed and rotate what should never have been there.

𝄞

Day one: the exposure report

Every runtime, framework and plugin version you run, mapped against current advisories, ranked by what is exploitable from the internet today. Plain language, one page, with the order of work.

♭

Days two to five: patches and proof

Upgrades, backports and mitigations shipped and tested, a compromise check for web shells, backdoors and odd logins, and a re-scan that shows each hole closed.

♯

Week two: hardened for next time

Dependency monitoring, a WAF rule set, an update pipeline your team can run, and a short handover so the next advisory is a routine Tuesday, not an incident.

Security watch

Sour notes,
patched.

October brought serious remote code execution flaws in PHP, Node.js and Next.js, the software behind a huge share of the web. Our team finds what is exposed, patches it fast and proves the hole is closed.

  1. Exposure auditWe map every runtime, framework and plugin version you run and flag what is exploitable.
  2. Emergency patchingUpgrades, backports and mitigations shipped fast, and tested so nothing else breaks.
  3. Compromise checkAttacks often begin before disclosure, so we hunt for web shells, backdoors and odd logins too.
  4. Hardened for next timeDependency monitoring, WAF rules and update pipelines, so the next advisory is a non-event.
Get a security check
Oct 21, 2026Critical · CVSS 9.2

PHP2Shell

CVE-2026-109618 · CVE-2026-109619

Unauthenticated remote code execution in PHP itself, demonstrated against WordPress, Drupal and Joomla. Exploit attempts started before the patch shipped.

Fixed inPHP 8.2.35 · 8.3.36 · 8.4.27 · 8.5.12
Oct 21, 2026High

Node.js Brotli RCE

CVE-2026-111497 + 9 more

An out-of-bounds write in the bundled Brotli decoder opens the door to remote code execution. One of ten CVEs fixed across the 22, 24 and 26 lines.

Fixed inNode.js 22.23.4 · 24.22.1 · 26.12.1
Oct 14, 2026Critical · CVSS 9.5

Next.js

CVE-2026-96889 · GHSA-673q-mjm6-r5xr

Two unauthenticated remote code execution flaws, one in image optimization and one in 'use cache' Cache Components.

Fixed inNext.js 15.5.28 · 16.4.1

Running something
on this list?

Get a security check