Google CaptchaWordPress extension · Bestwebsoft
CVE-2015-0890
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 · uneditedThe BestWebSoft Google Captcha (aka reCAPTCHA) plugin before 1.13 for WordPress allows remote attackers to bypass the CAPTCHA protection mechanism and obtain administrative access via unspecified vectors.
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 confidenceThe BestWebSoft Google Captcha (reCAPTCHA) plugin for WordPress versions before 1.13 contains a vulnerability allowing remote attackers to bypass the CAPTCHA protection mechanism entirely, enabling unauthorized administrative access to the WordPress site.
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
Google CaptchaWordPress extension
<= 1.12CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin versionCheck the BestWebSoft Google Captcha plugin version in WordPress admin under Plugins > Installed Plugins, or inspect the plugin's main PHP file (google-captcha.php) for the 'Version' header commentAffected if The displayed version is 1.12 or lower, or the Version header shows 1.12 or lower
-
Confirm the plugin is activeVerify the Google Captcha plugin is activated in WordPress under Plugins > Installed Plugins - look for 'Active' status under the plugin nameAffected if The plugin shows as Active and the version is 1.12 or lower
-
Check if CAPTCHA protection is enabledNavigate to Settings > Google Captcha in WordPress admin and examine the checkboxes for forms protected (login form, registration form, etc.)Affected if CAPTCHA protection is enabled on any form (login, registration, lost password, comments) and the plugin version is 1.12 or lower
-
Inspect plugin files for version markerAccess the WordPress wp-content/plugins/google-captcha folder via FTP or file manager, open google-captcha.php, and locate the version string in the plugin header commentsAffected if The file shows a version number <= 1.12
You are affected if the BestWebSoft Google Captcha plugin version is 1.12 or lower AND the plugin is active with CAPTCHA protection enabled on any WordPress forms.
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 BestWebSoft Google Captcha plugin to version 1.13 or later to remediate this vulnerability. Additionally, review user accounts for unauthorized administrative access and rotate credentials as a precaution.
Fix this in Google Captcha
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0890 — 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-2015-0890 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