dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-68075

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 8 weeks old

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 · unedited
Contributor Cross Site Scripting (XSS) in BNE Testimonials <= 2.0.8 versions.

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 · moderate confidence

Cross-Site Scripting (XSS) vulnerability in BNE Testimonials WordPress plugin versions 2.0.8 and below allows authenticated users with Contributor-level privileges to inject malicious JavaScript through testimonial input fields due to insufficient input sanitization.

MitigationUpdate BNE Testimonials plugin to the latest version; if no patch is available, disable the plugin until a fix is released.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify BNE Testimonials plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'BNE Testimonials' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder named 'bne-testimonials'
    Affected if The plugin folder exists in the WordPress installation
  2. Check the installed version of BNE Testimonials
    In WordPress Admin > Plugins, find BNE Testimonials and view the version number listed beneath the plugin name, or read the version from the plugin's main PHP file or readme.txt in /wp-content/plugins/bne-testimonials/
    Affected if The version number is 2.0.8 or lower
  3. Confirm the plugin is active
    In WordPress Admin > Plugins, verify that BNE Testimonials shows as 'Active' under the plugin status column
    Affected if The plugin is currently active and running on the site
  4. Verify Contributor role has access to testimonial functionality
    Check WordPress user roles under Users > Roles or use a role management plugin to confirm if Contributor-level users have the capability to create or edit testimonials (typically 'publish_testimonials' or 'edit_testimonials' capabilities)
    Affected if Contributor role users can access and submit testimonial forms on the site

The environment is affected if BNE Testimonials plugin version 2.0.8 or below is installed, active, and Contributor-level users can access testimonial input fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BNE Testimonials plugin to the latest version; if no patch is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

BNE Testimonials version 2.0.9 or later (latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate BNE Testimonials plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the updated plugin from the WordPress plugin repository and upload it manually
  6. 6. After updating, clear any caching plugins if applicable
  7. 7. Verify the plugin is functioning correctly on the frontend

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.5 h
2.5 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68075 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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