CVE-2025-39442
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in MessageMetric Review Wave – Google Places Reviews review-wave-google-places-reviews allows Stored XSS.This issue affects Review Wave – Google Places Reviews: from n/a through <= 1.4.7.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Review Wave Google Places Reviews WordPress plugin allows attackers to craft malicious requests that result in Stored XSS. The lack of proper CSRF protection (missing nonce/token validation) combined with insufficient input sanitization enables attackers to inject malicious scripts that persist in the review data and execute in other users' browsers.
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 Review Wave plugin is installedNavigate to WordPress admin > Plugins > Installed Plugins and search for 'Review Wave Google Places Reviews' or 'review-wave'Affected if The plugin appears in the installed plugins list
-
Identify installed plugin versionClick on the plugin in the WordPress plugins list to view its details, or check the plugin header in wp-content/plugins/review-wave/includes/*.php for 'Version:' tagAffected if A version number is displayed (compare to any vendor release notes for patched versions)
-
Confirm plugin is activeCheck that the Review Wave plugin shows as 'Active' in the WordPress plugins admin pageAffected if Plugin status shows 'Active' (inactive plugins cannot be exploited)
-
Check for nonce verification in review submissionInspect the plugin PHP files that handle review submissions (typically in admin or public handlers) for presence of wp_verify_nonce, check_admin_referer, or nonce_field calls before processing POST/GET requestsAffected if No nonce verification code is found in the review handling functions - this indicates the CSRF vulnerability is present
-
Inspect input sanitization on review dataReview the same plugin PHP files for use of sanitization functions (sanitize_text_field, esc_html, esc_attr, wp_kses) on review data before storage or outputAffected if Input sanitization is missing or inadequate on review data fields
If the Review Wave Google Places Reviews plugin is installed and active, and code inspection reveals missing nonce validation combined with weak input sanitization in review handling functions, the environment is vulnerable to CVE-2025-39442.
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 anti-CSRF tokens (nonces) on all state-changing operations and apply proper input sanitization and output encoding to prevent stored XSS. Update to a patched version when released by the vendor.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39442 — 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-2025-39442 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