CVE-2026-42639
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 · uneditedUnauthenticated SQL Injection in GD Rating System <= 3.6.2 versions.
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 confidenceAn unauthenticated SQL injection vulnerability exists in the GD Rating System WordPress plugin versions 3.6.2 and below. This critical flaw (CVSS 9.3) allows remote attackers to inject malicious SQL queries without any authentication, potentially leading to data exfiltration or complete database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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.
-
Check installed GD Rating System plugin versionNavigate to WordPress Admin > Plugins > Installed Plugins, locate 'GD Rating System', and read the version number from the plugin description. Alternatively, inspect /wp-content/plugins/gd-rating-system/plugin.php and look for the 'Version:' header comment.Affected if Version displayed is 3.6.2 or lower
-
Confirm the plugin is activeIn WordPress Admin > Plugins, verify that GD Rating System shows as 'Active' under the plugin status.Affected if Plugin is installed AND active - the vulnerability is unauthenticated so no user authentication is required for exploitation
-
Check for unusual database queries in logsReview web server access logs (Apache/nginx) and WordPress debug logs for requests to GD Rating System endpoints containing SQL keywords (UNION, SELECT, INSERT, UPDATE, DELETE, DROP) in query parameters, especially around rating submission or poll voting functions.Affected if Log entries show SQL injection patterns in requests to /wp-content/plugins/gd-rating-system/ endpoints
-
Inspect plugin database tables for unauthorized changesCheck WordPress database tables (particularly those prefixed with wp_gdrts_ if they exist) for unexpected tables, modified records, or unfamiliar data that could indicate successful exploitation.Affected if Database contains unexpected tables, records, or modified data in rating-related tables
You are affected if GD Rating System version 3.6.2 or lower is installed and active on your WordPress site - the unauthenticated SQL injection requires no user authentication and the plugin simply needs to be enabled.
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 dataImmediately update GD Rating System to the latest patched version. If no update is available, disable the plugin temporarily and review server logs for signs of exploitation. Consider implementing a WAF rule to block SQL injection patterns as a compensating control.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42639 — 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-2026-42639 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