Gd Star RatingWordPress extension · Dev4press
CVE-2014-2839
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 · uneditedSQL injection vulnerability in the GD Star Rating plugin 19.22 for WordPress allows remote administrators to execute arbitrary SQL commands via the s parameter in the gd-star-rating-stats page to wp-admin/admin.php.
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 confidenceSQL injection vulnerability in GD Star Rating plugin version 19.22 for WordPress allows authenticated administrators to execute arbitrary SQL commands via the unsanitized 's' parameter on the gd-star-rating-stats admin page (wp-admin/admin.php). The vulnerability stems from improper input sanitization allowing SQL command injection.
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 Star RatingWordPress extension
= 19.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 GD Star Rating plugin is installedNavigate to WordPress admin Plugins page or inspect the wp-content/plugins/ directory for a gd-star-rating folderAffected if The plugin folder exists in the WordPress installation
-
Identify the installed versionView the plugin details in WordPress admin (Plugins > GD Star Rating) or open gd-star-rating.php and check the Version header commentAffected if The version listed is exactly 19.22
-
Verify administrator access existsCheck WordPress users with Administrator role via wp-admin/users.php or query the wp_users and wp_usermeta tablesAffected if At least one user account with administrator privileges exists in WordPress
-
Confirm the vulnerable admin page is accessibleCheck if the gd-star-rating-stats page is available by accessing wp-admin/admin.php?page=gd-star-rating-stats with admin credentialsAffected if The gd-star-rating-stats admin page loads without errors
A user is affected if the GD Star Rating plugin version 19.22 is installed, active, and an administrator account can access the gd-star-rating-stats admin page with the vulnerable 's' parameter.
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 the GD Star Rating plugin to a patched version that addresses the SQL injection vulnerability. If no patched version is available, deactivate and remove the plugin and migrate to an alternative rating solution.
Fix this in Gd Star Rating
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $2,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2839 — 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-2014-2839 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