ReviewxWordPress extension · Wpdeveloper
CVE-2022-46809
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 Formula Elements in a CSV File vulnerability in WPDeveloper ReviewX – Multi-criteria Rating & Reviews for WooCommerce.This issue affects ReviewX – Multi-criteria Rating & Reviews for WooCommerce: from n/a through 1.6.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 · moderate confidenceThis is a CSV Injection (Formula Injection) vulnerability in the ReviewX WordPress plugin. The plugin fails to properly sanitize CSV exports, allowing injection of formula characters (=, +, -, @, tab, CR) that spreadsheet applications interpret as formula commands. When users open exported CSV files, this can lead to arbitrary code execution (Microsoft Excel) or data exfiltration (Google Sheets).
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.7CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installedCheck WordPress admin under Plugins > Installed Plugins for 'ReviewX' or inspect wp-content/plugins/ directory for reviewx folderAffected if ReviewX plugin folder exists in the WordPress plugins directory
-
Determine installed ReviewX versionView the plugin details in WordPress admin (Plugins > Installed Plugins > ReviewX) or read the version from reviewx/readme.txt or reviewx/reviewx.php headerAffected if The displayed version number is 1.6.7 or lower
-
Confirm CSV export feature is accessibleNavigate to ReviewX settings panel in WordPress admin and locate any export, review export, or CSV download options under the plugin menuAffected if CSV export functionality is present and available in the plugin interface
-
Check for existing exported CSV filesSearch the wp-content/uploads/ directory or any designated export folders for recently created .csv files that may have been generated by ReviewXAffected if CSV files exported by ReviewX exist on the server
You are affected if ReviewX plugin version is 1.6.7 or lower and you have used or intend to use the CSV export feature to generate review data files.
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 ReviewX plugin to version 1.6.8 or later. Until patched, avoid opening exported CSV files from the plugin in spreadsheet applications; use text editors instead.
Fix this in Reviewx
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46809 — 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-2022-46809 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