ReviewxWordPress extension · Wpdeveloper
CVE-2024-29812
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 ReviewX allows Stored XSS.This issue affects ReviewX: from n/a through 1.6.22.
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 confidenceReviewX plugin before version 1.6.22 contains a stored cross-site scripting (XSS) vulnerability where user-supplied input is not properly sanitized before being rendered in web pages, allowing malicious scripts to be permanently stored and executed when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ReviewxWordPress extension
<= 1.6.22CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 ReviewX plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'ReviewX' in the list of active pluginsAffected if ReviewX plugin appears in the installed plugins list and is active
-
Check installed ReviewX versionIn WordPress admin, go to Plugins > Installed Plugins > ReviewX, or check the plugin file header in wp-content/plugins/reviewx/includes/Reviewx.php for the 'Version' commentAffected if The displayed version number is 1.6.22 or lower
-
Identify review submission endpointsCheck the plugin settings and frontend review forms to locate where users can submit reviews (typically found at /?reviewx_submit or via AJAX endpoints in the plugin)Affected if A review submission form exists and accepts user input without requiring admin-level authentication
-
Inspect stored review data for sanitizationAccess the WordPress database (via phpMyAdmin or wp-cli) and query the reviewx_reviews table or related meta tables to examine stored review content for raw HTML or script tagsAffected if Stored review entries contain unescaped HTML tags such as <script>, <img onerror>, or javascript: URIs in any review field
You are affected if ReviewX plugin version 1.6.22 or lower is installed and active, and review submissions are being accepted and stored without proper sanitization.
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 dataApply the vendor patch (upgrade to version 1.6.23 or later) which implements proper input sanitization and output encoding to neutralize malicious script payloads.
Fix this in Reviewx
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29812 — 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-2024-29812 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