Security readout for executives and security teams
Plain-English summary
This CVE affects the Captcha Code WordPress plugin version 2.7 and earlier. A successful CSRF attack could trick an authenticated site user into changing plugin settings. Business impact is usually limited, but exposed WordPress sites should treat it as a maintenance and integrity risk.
Executive priority
Handle in normal vulnerability remediation cycles, faster for public WordPress sites where plugin settings affect security workflows. There is no provided evidence of active exploitation, but affected versions should not remain deployed indefinitely.
Technical view
CVE-2022-37411 is a CWE-352 CSRF issue in Vinoj Cardoza's Captcha Code plugin for WordPress, affecting versions <= 2.7. The CVSS 3.1 score is 5.4, with network attack vector, no privileges required, user interaction required, and low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites using Captcha Code plugin version 2.7 or earlier. The bundle provides no CPEs and no installation telemetry, so environment inventory is required.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. User interaction is required, consistent with CSRF. Patchstack describes the outcome as plugin settings update, but no exploit details are included here.
Researcher notes
Evidence is narrow but consistent: CVE metadata, Patchstack reference, and WordPress plugin reference identify CSRF in Captcha Code <= 2.7. The bundle does not provide a patched version, proof-of-concept status, or exploitation telemetry.
Mitigation direction
- Inventory WordPress sites for the Captcha Code plugin.
- Confirm whether installed versions are 2.7 or earlier.
- Check WordPress.org and Patchstack for vendor guidance and fixed versions.
- Upgrade to a vendor-confirmed fixed release, or disable/remove the plugin.
- Review plugin settings for unexpected changes after remediation.
Validation and detection
- Verify the plugin slug and version on each WordPress site.
- Flag any Captcha Code installation at version 2.7 or earlier.
- Confirm remediation status against vendor or WordPress.org guidance.
- Review administrative logs for unexpected plugin setting changes.
- Retest affected sites after update, disablement, or removal.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-37411 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/captcha-code-authentication/wordpress-captcha-code-plugin-2-7-cross-site-request-forgery-csrf-vulnerability-leading-to-plugin-settings-update/_s_id=cveCVE reference · x_refsource_CONFIRM
- https://wordpress.org/plugins/captcha-code-authentication/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.