dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-62933

HIGH · 7.1 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Prakash Awesome Testimonials awesome-testimonials allows Stored XSS.This issue affects Awesome Testimonials: from n/a through <= 2.2.1.

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 Request Forgery (CSRF) vulnerability in the Awesome Testimonials WordPress plugin enables attackers to trick authenticated administrators into submitting malicious requests that inject persistent JavaScript (Stored XSS) into testimonial data. When other users view the affected testimonials, the injected scripts execute in their browsers.

MitigationUpdate the Awesome Testimonials plugin to the latest version which should include CSRF token validation and proper input sanitization. Until patched, restrict administrative access and monitor for suspicious testimonial submissions.

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 checks

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

  1. Verify Awesome Testimonials plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Awesome Testimonials' in the list. Note the installed version number displayed.
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    Compare the installed version number against the version that includes the fix (the latest version on the WordPress plugin repository or the version noted in the security advisory).
    Affected if The installed version is older than the patched version containing CSRF token validation and proper input sanitization
  3. Identify admin-accessible testimonial submission endpoints
    Navigate to the WordPress admin section where testimonial submissions are managed (typically under the plugin menu or Comments section). Determine if testimonial creation/editing forms are accessible to authenticated administrators.
    Affected if Admin users can submit or edit testimonials through the WordPress admin interface
  4. Inspect stored testimonial data for malicious content
    Access the testimonial database table (usually via phpMyAdmin or WP Admin > Comments if testimonials are stored as comments) or use a database query to examine testimonial_content fields for unsanitized HTML, script tags, or JavaScript event handlers such as onerror, onload, or onclick.
    Affected if Testimonial database entries contain raw HTML, script tags, or JavaScript event handler attributes that were not sanitized upon storage
  5. Review HTTP requests for missing CSRF protections
    Use browser developer tools or a proxy to intercept the HTTP request when submitting a testimonial through the admin interface. Inspect the request headers and payload for a valid CSRF token or nonce parameter.
    Affected if The testimonial submission request lacks a CSRF token or nonce validation parameter

A user is affected if the Awesome Testimonials plugin is installed with a version lacking CSRF protection, the plugin allows admin-accessible testimonial submissions, and stored testimonial data contains unsanitized JavaScript or HTML content.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Awesome Testimonials plugin to the latest version which should include CSRF token validation and proper input sanitization. Until patched, restrict administrative access and monitor for suspicious testimonial submissions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62933 — 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-62933 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