# CVE-2026-2112: Dam Spam <= 1.0.8 - Cross-Site Request Forgery to Arbitrary Pending Comment Deletion

> Unauthenticated attackers can delete all pending comments by tricking an admin into clicking a link due to missing nonce verification.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 18 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qj9g-q4j9-47hp

## What is CVE-2026-2112?

CVE-2026-2112 is a medium-severity vulnerability in webguyio Dam Spam, published on 18 Feb 2026. 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

The Dam Spam plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.8. This is due to missing nonce verification on the pending comment deletion action in the cleanup page. This makes it possible for unauthenticated attackers to delete all pending comments via a forged request granted they can trick an admin into performing an action such as clicking on a link.

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

## Which versions are affected by CVE-2026-2112?


## How do I fix CVE-2026-2112?

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

## Is CVE-2026-2112 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2112 and fix it if it is affected.

What it is: CVE-2026-2112 is a medium-severity vulnerability in webguyio Dam Spam, published on 18 Feb 2026. 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-2026-2112 in the wild and no public exploit code.

Affected product: webguyio Dam Spam. 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-2026-2112/ (Markdown: https://insights.sbomify.com/CVE-2026-2112/index.md)
```

## Sources

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

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