CVE-2026-8039
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 Fancy Testimonials plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author' shortcode attribute in the 'testimonial' shortcode in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Fancy Testimonials WordPress plugin fails to sanitize the 'author' attribute in the 'testimonial' shortcode and does not escape output, allowing stored XSS. Authenticated users with Contributor-level permissions can inject malicious JavaScript via the shortcode 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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.
-
Verify Fancy Testimonials plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Fancy Testimonials', or check the wp-content/plugins directory for the plugin folderAffected if The plugin is installed and active
-
Determine the installed plugin versionIn the Plugins admin page, click on the plugin to view its details and read the Version number, or open the main plugin PHP file and check the Version header in the plugin comment blockAffected if The installed version has not yet received the security fix (compare your version against the current version on WordPress.org)
-
Identify use of the vulnerable testimonial shortcodeSearch WordPress posts, pages, and widgets for the shortcode [testimonial] that includes an author parameter, for example [testimonial author="value"]Affected if The testimonial shortcode with an author attribute exists in any published content
-
Verify author parameter sanitization in codeOpen the plugin's main PHP file, locate the shortcode handler function, and check whether the author attribute is processed with sanitize_text_field() before useAffected if The author parameter is used without sanitize_text_field() or equivalent sanitization function
-
Verify author output escaping in codeIn the shortcode output generation, locate where the author value is rendered and check whether esc_html() or esc_attr() is used when outputting the author valueAffected if The author value is output without esc_html() or esc_attr() escaping
The environment is affected if the Fancy Testimonials plugin is active, the vulnerable shortcode with author parameter is in use, and the code lacks proper sanitization (sanitize_text_field) and escaping (esc_html/esc_attr) for the author attribute
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 dataUpdate to a patched version of the plugin once available, or implement proper input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) on the author parameter in the shortcode handler.
- 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-8039 — 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-8039 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