CVE-2026-25347
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Acato WP REST Cache wp-rest-cache allows Stored XSS.This issue affects WP REST Cache: from n/a through <= 2026.1.0.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the Acato WP REST Cache WordPress plugin. The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing authenticated attackers to inject malicious JavaScript that executes when other users view affected pages.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify Acato WP REST Cache plugin is installedCheck the WordPress plugins directory for the Acato WP REST Cache plugin folder, or list all installed plugins via wp-cli: wp plugin list --status=active,allAffected if The plugin folder 'acato-wp-rest-cache' or similar exists in /wp-content/plugins/ and appears in the plugin list
-
Identify the installed plugin versionRead the main plugin file (usually acato-wp-rest-cache.php) and look for the version defined in the plugin header, or use: wp plugin list --fields=name,version | grep -i acatoAffected if The version shown does not match a patched version (compare to the latest version available from the WordPress plugin repository)
-
Confirm the plugin is activeCheck if the plugin status is 'active' using WordPress admin, database query: SELECT * FROM wp_options WHERE option_name = 'active_plugins'; or wp-cli: wp plugin status acato-wp-rest-cacheAffected if The plugin appears in the active plugins list
-
Examine stored data for unsanitized user inputIf the plugin stores REST API cache data, query the database tables where cache is stored (look for tables prefixed wp_acato_ or similar cache tables) and inspect stored values for HTML/script tagsAffected if Database contains cache entries with raw user-supplied input that includes HTML tags, script elements, or JavaScript event handlers without encoding
-
Check REST API endpoints for user input captureReview the plugin code in the includes/ or classes/ directory for functions handling REST API requests, particularly any that accept user input and store or display itAffected if The plugin processes and stores REST API parameters without applying sanitization functions like sanitize_text_field, esc_html, or esc_attr
If the Acato WP REST Cache plugin is installed, active, and processes user-supplied REST API parameters without proper sanitization before storage or rendering, the environment is affected by this stored XSS vulnerability.
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 dataImplement proper input validation and output encoding/sanitization for all user-supplied data before rendering in HTML or JavaScript contexts. Update the plugin to the latest version once a patch is available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25347 — 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-25347 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