Security readout for executives and security teams
Plain-English summary
This is a medium-risk WordPress plugin issue. A remote attacker could abuse missing CSRF protections to make a logged-in user trigger unwanted Subscribe To Comments Reloaded actions, including changing settings, resetting options, or managing subscriptions. It requires user interaction and is not listed as known exploited in KEV.
Executive priority
Treat as a moderate-priority WordPress maintenance issue. It is not evidence of emergency exploitation, but affected sites should be updated or have the plugin disabled because abuse could alter site behavior and subscription data.
Technical view
CVE-2022-29414 covers 13 CWE-352 CSRF vulnerabilities in WPKube Subscribe To Comments Reloaded for WordPress versions <= 211130. The CVSS 3.1 score is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites running Subscribe To Comments Reloaded version 211130 or earlier. Risk is higher where users with access to plugin settings or subscription management can be socially induced to visit attacker-controlled content.
Exploitation context
The provided sources do not state active exploitation, and this CVE is not marked KEV. The vulnerability is CSRF, so practical abuse depends on tricking an authorized WordPress user into taking an unintended browser-mediated action.
Researcher notes
Evidence identifies multiple CSRF-prone plugin actions but does not provide patch details in the supplied bundle. Validate exposure by version and plugin presence. Avoid assuming compromise without logs or configuration changes supporting it.
Mitigation direction
- Inventory WordPress sites using Subscribe To Comments Reloaded.
- Update the plugin according to vendor or WordPress.org guidance.
- Disable or remove the plugin if a safe version cannot be confirmed.
- Review plugin settings and subscriptions for unauthorized changes.
Validation and detection
- Check installed plugin version on each WordPress site.
- Confirm whether any instance runs version 211130 or earlier.
- Review administrative logs for unexpected plugin option changes.
- Verify subscription records were not added, updated, or deleted unexpectedly.
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-29414 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://wordpress.org/plugins/subscribe-to-comments-reloaded/CVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/subscribe-to-comments-reloaded/wordpress-subscribe-to-comments-reloaded-plugin-211130-multiple-cross-site-request-forgery-csrf-vulnerabilitiesCVE 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.