dbcve.org
Subscribe To Comments ReloadedWordPress extension · Wpkube

CVE-2022-29414

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-29
Fix available
A fix is available. Upgrade to after 211130 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Multiple (13x) Cross-Site Request Forgery (CSRF) vulnerabilities in WPKube's Subscribe To Comments Reloaded plugin <= 211130 on WordPress allows attackers to clean up Log archive, download system info file, plugin system settings, plugin options settings, generate a new key, reset all options, change notifications settings, management page settings, comment form settings, manage subscriptions > mass update settings, manage subscriptions > add a new subscription, update subscription, delete Subscription.

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 confidence

The Subscribe To Comments Reloaded WordPress plugin <= version 211130 lacks proper anti-CSRF token validation on 13 different administrative action endpoints. Attackers can trick authenticated administrators into unknowingly executing configuration changes (plugin settings, notifications, comment form settings), subscription management (add/update/delete subscriptions, mass updates), and system operations (reset options, generate keys, download system info, clean logs) by forcing their browser to send malicious requests.

MitigationImplement WordPress nonces (wp_verify_nonce and wp_create_nonce) on all state-changing POST/GET requests, including proper referer/origin validation, across all 13 affected endpoints.

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
Subscribe To Comments ReloadedWordPress extension
Affected:<= 211130

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Subscribe To Comments Reloaded' or check the plugin header comment in the main PHP file (usually stcr-plugin.php or subscribe-to-comments-reloaded.php)
    Affected if The installed version is 211130 or any version number lower than 211130 (e.g., 211115, 210900)
  2. Inspect admin action files for nonce validation
    Examine the main plugin PHP file and any admin-related PHP files for the presence of wp_verify_nonce or wp_create_nonce function calls around state-changing code (POST/GET handlers for settings, subscriptions, system operations)
    Affected if The code handling administrative actions (settings changes, subscription management, system operations) lacks wp_verify_nonce or check_admin_referer calls
  3. Check plugin settings page accessibility
    Attempt to access the plugin's admin settings page via WordPress admin panel and inspect the HTML forms for hidden nonce fields
    Affected if The plugin settings forms (comment form settings, notification settings, subscription management) do not contain wp_nonce_field generated nonce inputs
  4. Review endpoint request handling
    Use browser developer tools or a proxy to observe HTTP requests when saving plugin settings or performing subscription actions; check if requests include a '_wpnonce' or similar token parameter
    Affected if Administrative actions (adding/updating/deleting subscriptions, modifying settings, resetting options) can be performed without a valid nonce token in the request

You are affected if the Subscribe To Comments Reloaded plugin version is 211130 or lower AND administrative actions can be executed without requiring a valid WordPress nonce token.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 211130
Interim mitigation

Implement WordPress nonces (wp_verify_nonce and wp_create_nonce) on all state-changing POST/GET requests, including proper referer/origin validation, across all 13 affected endpoints.

Recommended fix Moderate confidence

Version 221025 or later (any version after 211130 that contains the security fix)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "Subscribe To Comments Reloaded" in the plugin list
  4. If an update is available, click "Update Now" to update to the latest version
  5. Alternatively, you can manually download the latest version from wordpress.org/plugins/subscribe-to-comments-reloaded/ and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is working correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Subscribe To Comments Reloaded Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29414 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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