Wp CaptchaWordPress extension · Devnath Verma
CVE-2023-44236
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Devnath verma WP Captcha plugin <= 2.0.0 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Captcha WordPress plugin by Devnath verma affecting all versions 2.0.0 and below. The flaw allows remote attackers to induce authenticated users to perform unwanted actions on the plugin via crafted requests.
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 CaptchaWordPress extension
<= 2.0.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify WP Captcha plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'WP Captcha' by Devnath Verma in the listAffected if Plugin is present in the installation
-
Check installed version of WP CaptchaIn Plugins list, click on the WP Captcha plugin to view its details, or check the plugin header comment in /wp-content/plugins/wp-captcha/wp-captcha.php for the Version fieldAffected if Version is 2.0.0 or lower (any version <= 2.0.0)
-
Confirm plugin is activeIn Plugins > Installed Plugins, verify the WP Captcha plugin has the 'Active' status indicatorAffected if Plugin is currently active and available to authenticated users
You are affected if WP Captcha by Devnath Verma is installed, active, and running version 2.0.0 or lower, as this version range lacks CSRF protection on admin actions.
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.
dbcve · scopedUpdate WP Captcha plugin to the latest available version. If no patched version exists, consider removing the plugin until a fix is released, or implement additional CSRF tokens on plugin admin actions.
Latest version of WP Captcha plugin (contact developer or check plugin repository for version beyond 2.0.0 that addresses CVE-2023-44236)
- Check the current version of the WP Captcha plugin installed on your WordPress site
- Navigate to Plugins > Installed Plugins > WP Captcha to verify the current version number
- Check the WordPress plugin repository or contact the plugin developer (Devnath verma) for information on the fixed version that addresses CVE-2023-44236
- Update the WP Captcha plugin to the latest available version that includes the security fix for the CSRF vulnerability
- After updating, verify the plugin is functioning correctly and test CAPTCHA functionality
- Ensure WordPress core and other plugins are also kept up to date
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Captcha
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44236 — 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-2023-44236 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