Universal Star RatingWordPress extension · Universal Star Rating Project
CVE-2022-46867
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 Chasil Universal Star Rating plugin <= 2.1.0 version.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Chasil Universal Star Rating WordPress plugin version 2.1.0 and below. The plugin lacks proper anti-CSRF tokens on state-changing operations, allowing attackers to trick authenticated users into performing unintended actions such as manipulating ratings.
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
Universal Star RatingWordPress extension
<= 2.1.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Universal Star Rating' or 'Chasil Universal Star Rating', or check the /wp-content/plugins/ directory for a folder named 'universal-star-rating' or similar.Affected if The plugin is not present in the WordPress installation.
-
Determine installed versionIn the WordPress plugins list, look at the version number displayed next to the Universal Star Rating plugin. Alternatively, open the main plugin PHP file (usually includes a version comment in the header) or check the plugin's main file for a 'Version:' header comment.Affected if Version displayed is 2.1.0 or lower.
-
Identify rating submission handlersExamine the plugin PHP files for functions that handle rating submissions or state-changing operations. Look for AJAX handlers (wp_ajax_* hooks) or form processing code that modifies rating data in the database.Affected if The plugin processes rating submissions via POST requests without visible evidence of CSRF protection.
-
Check for nonce validation in rating handlersSearch the plugin's PHP files for state-changing functions (rating submission, vote handling) and verify if they include nonce verification calls such as wp_verify_nonce(), check_admin_referer(), or wp_nonce_field() before processing the request.Affected if Rating handling functions process requests without validating a nonce token.
-
Inspect HTML output for nonce fieldsIf the plugin outputs forms or AJAX buttons for submitting ratings, view the page source (or inspect the HTML) and check if hidden nonce fields are included in rating submission forms.Affected if Rating forms are rendered without hidden nonce token fields.
A user is affected if the Universal Star Rating plugin version 2.1.0 or lower is installed and its rating submission handlers process requests without validating anti-CSRF nonce tokens.
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 (synchronizer token pattern) on all state-changing operations within the plugin and validate these tokens server-side on every POST/PUT/DELETE request.
Fix this in Universal Star Rating
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46867 — 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-46867 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