CVE-2026-12685
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe EscortWP escortwp WordPress theme through 3.6.2 was distributed with a vendor-authored, obfuscated backdoor that lets an unauthenticated attacker who supplies a hard-coded, per-build key permanently delete all of the site's content, and that covertly transmits the site URL, administrator email address, and license key to a third-party server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe EscortWP WordPress theme through v3.6.2 contains a vendor-authored obfuscated backdoor accessible to unauthenticated attackers possessing a per-build hard-coded key. The backdoor enables permanent deletion of all site content and covertly exfiltrates the site URL, administrator email, and license key to a third-party server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify EscortWP theme installation and versionNavigate to wp-content/themes/escortwp/ and open style.css to find the 'Version:' header, or query via WordPress admin dashboard under Appearance > ThemesAffected if The installed version is 3.6.2 or lower
-
Locate obfuscated backdoor codeSearch theme directory for PHP files containing base64_decode, eval, or str_rot13 functions, particularly in unexpected files like footer.php, functions.php, or recently modified filesAffected if Obfuscated PHP code is found that executes remote commands or manipulates database content
-
Search for hard-coded authentication keyGrep theme files for long random-looking strings (30+ characters) that may serve as the per-build key, or search for patterns like 'key' or 'auth' in encoded sectionsAffected if A hard-coded key value is present in theme files
-
Inspect server access logs for backdoor triggersReview HTTP access logs (typically in /var/log/apache2/ or /var/log/nginx/) for POST requests to theme files with parameters matching the backdoor functionality (content deletion or data exfiltration)Affected if Unauthenticated POST requests targeting theme files contain suspicious parameters or the hard-coded key value
-
Check for unauthorized data exfiltrationMonitor network logs or server outgoing connections for outbound requests to unfamiliar third-party domains originating from PHP processes, particularly those containing the site URL, admin email, or license key as URL parametersAffected if Outbound requests containing WordPress site metadata are sent to unknown external servers
The environment is affected if the EscortWP theme version is 3.6.2 or lower, or if obfuscated backdoor code with a hard-coded key is found in the theme files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately remove the compromised theme from the WordPress installation, treat the site as potentially compromised, change all credentials (admin passwords, license keys, API keys), and restore from a known-clean backup if any unauthorized changes are detected.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12685 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data