# CVE-2022-29414: WordPress Subscribe To Comments Reloaded plugin <= 211130 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities

> Attackers can trick users into modifying plugin settings, deleting subscriptions, or exposing system info via CSRF in Subscribe To Comments Reloaded.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Apr 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-g87x-9qg3-cfrp

## What is CVE-2022-29414?

CVE-2022-29414 is a medium-severity vulnerability in WPKube Subscribe To Comments Reloaded (WordPress plugin), published on 29 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-29414?

It affects 1 product.


Products: Wpkube Subscribe to Comments Reloaded.

## How do I fix CVE-2022-29414?

No fix has been published for CVE-2022-29414 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-29414 being exploited?

There is no known exploitation of CVE-2022-29414 in the wild and no public exploit code.

## Other vulnerabilities in WPKube Subscribe To Comments Reloaded (WordPress plugin)

- [CVE-2024-31249](https://insights.sbomify.com/CVE-2024-31249/): WordPress Subscribe To Comments Reloaded plugin <= 220725 - Sensitive Data Exposure vulnerability (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29414 and fix it if it is affected.

What it is: CVE-2022-29414 is a medium-severity vulnerability in WPKube Subscribe To Comments Reloaded (WordPress plugin), published on 29 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29414 in the wild and no public exploit code.

Affected product: WPKube Subscribe To Comments Reloaded (WordPress plugin). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-29414/ (Markdown: https://insights.sbomify.com/CVE-2022-29414/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-29414
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-29414
- OSV: https://osv.dev/vulnerability/CVE-2022-29414

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-29414/
Summaries are generated and may contain mistakes; the official description above is the record.