dbcve.org
Gd Rating SystemWordPress extension · Dev4press

CVE-2024-25093

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 3.5.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 ('Cross-site Scripting') vulnerability in Milan Petrovic GD Rating System allows Stored XSS.This issue affects GD Rating System: from n/a through 3.5.

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 confidence

A stored Cross-site Scripting (XSS) vulnerability exists in GD Rating System where user-supplied input (likely rating submissions, comments, or review content) is not properly sanitized or escaped before being rendered in HTML pages. An attacker can inject malicious JavaScript code that executes in the browsers of other users who view the affected content.

MitigationImplement proper output encoding/escaping for all user-supplied data before rendering in HTML context, combined with input validation. Consider adding Content-Security-Policy headers as a defense-in-depth measure.

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
Gd Rating SystemWordPress extension
Affected:< 3.5.1

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check the installed GD Rating System version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'GD Rating System'. Note the version number displayed. Alternatively, check the plugin header in the main plugin file (typically gd-rating-system.php in wp-content/plugins/gd-rating-system/)
    Affected if The installed version is lower than 3.5.1 (for example, 3.5.0, 3.4.x, or earlier)
  2. Identify user input entry points
    Visit the pages on your site where the rating system is active. Look for places where users can submit ratings, reviews, comments, or any textual content that gets stored and displayed publicly
    Affected if The plugin accepts and stores user-submitted text content (such as review text, rating comments, or user responses) that is rendered on the frontend
  3. Verify if submitted content appears in HTML output without encoding
    Submit a test rating with a simple HTML tag in the text field (such as <script>alert(1)</script> or <b>test</b>). Then view the page where this content is displayed. Inspect the page source to see if the tags are rendered as raw HTML (visible in source) or if they are encoded (appearing as &lt;script&gt;)
    Affected if The submitted HTML tags are rendered as actual HTML elements or appear unmodified in the page source, indicating missing output encoding
  4. Inspect plugin source for sanitization functions
    Examine the plugin PHP files, particularly those handling rating submission and display (look for files related to rendering, shortcodes, or template output). Search for functions like echo, print, or printf that output user data without passing through sanitization functions such as esc_html, esc_attr, or wp_kses
    Affected if User-supplied data from ratings or reviews is output directly to HTML without passing through WordPress sanitization functions

A site is affected if GD Rating System version is below 3.5.1 AND the plugin accepts user-submitted text content that is rendered on frontend pages without proper output encoding.

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 3.5.1 or later
Fixed in 3.5.1
Interim mitigation

Implement proper output encoding/escaping for all user-supplied data before rendering in HTML context, combined with input validation. Consider adding Content-Security-Policy headers as a defense-in-depth measure.

Recommended fix High confidence

GD Rating System version 3.5.1

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'GD Rating System' in the plugin list
  4. Click 'Update Now' if an update is available, or manually upload version 3.5.1 of the plugin
  5. Verify the plugin version shows 3.5.1 after updating
  6. Clear any site caching mechanisms if applicable
  7. Test the rating functionality to ensure it works correctly post-update

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

Fix this in Gd Rating System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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