dbcve.org
Wp PostratingsWordPress extension · Lesterchan

CVE-2024-39659

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 1.91.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Lester ‘GaMerZ’ Chan WP-PostRatings allows Stored XSS.This issue affects WP-PostRatings: from n/a through 1.91.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 · high confidence

Stored XSS vulnerability in WP-PostRatings plugin allows attackers to inject malicious JavaScript through the ratings functionality. The plugin fails to properly sanitize user input before rendering it in web pages, leading to persistent script execution when other users view the affected content.

MitigationUpdate WP-PostRatings to the latest version after 1.91.1 which should contain the patched code. If no patched version is available, disable the plugin or implement input validation at the web application firewall level until a fix is released.

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
Wp PostratingsWordPress extension
Affected:< 1.91.2

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
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 checks

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

  1. Verify WP-PostRatings plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate WP-PostRatings in the list. The version number is displayed below the plugin name.
    Affected if The displayed version is lower than 1.91.2 (e.g., 1.91.1, 1.91.0, or earlier)
  2. Confirm ratings functionality is active
    Check if the WP-PostRatings widget or shortcode is deployed on your site. Look for rating displays on posts or pages, or inspect your WordPress database for entries in the wp_postratings table.
    Affected if The plugin is active and ratings functionality is being used on any post or page on your site
  3. Inspect database for unsanitized input in ratings
    Access your WordPress database (via phpMyAdmin or command line) and query the postratings_log table or equivalent: SELECT * FROM wp_postratings_log ORDER BY rating_timestamp DESC LIMIT 50; Look at the rating_user (user-provided rating text/comment) fields.
    Affected if Any rating_user field contains HTML, script tags, or JavaScript code such as <script>, javascript:, onerror=, or other suspicious markup
  4. Check page source for unescaped rating content
    View a page with active ratings, right-click and select 'View Page Source', then search for the rendered rating content. Compare the displayed output to the original input stored in the database.
    Affected if The rendered HTML on the page contains unescaped characters (e.g., actual <script> tags visible in the source rather than &lt;script&gt;)

Your site is affected if WP-PostRatings version is below 1.91.2 and the plugin is actively displaying ratings that could contain unsanitized user input in the page output.

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.

dbcve · scoped
Upgrade available Upgrade to 1.91.2 or later
Fixed in 1.91.2
Interim mitigation

Update WP-PostRatings to the latest version after 1.91.1 which should contain the patched code. If no patched version is available, disable the plugin or implement input validation at the web application firewall level until a fix is released.

Recommended fix High confidence

WP-PostRatings 1.91.2

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate WP-PostRatings in the plugin list.
  4. 4. Click 'Update Now' if an update is available, or manually upload version 1.91.2.
  5. 5. Verify the plugin is running version 1.91.2 after updating.
  6. 6. Test the rating functionality to ensure the plugin still works correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Postratings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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