LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-2112 affects the Dam Spam WordPress plugin through version 1.0.8. An attacker cannot use it alone; they must trick a logged-in administrator into clicking or loading a crafted request. If successful, the attacker can delete all pending comments, disrupting moderation workflows but not taking over the site.

Executive priority

Treat as a routine, time-bound WordPress plugin remediation. It is not a site takeover issue, but it can disrupt comment moderation and erase pending user submissions if an administrator is tricked. Address during the next plugin maintenance cycle, sooner for comment-heavy sites.

Technical view

This is a CSRF issue, CWE-352, caused by missing nonce verification on the cleanup page’s pending comment deletion action. The reported impact is arbitrary deletion of pending comments. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges, user interaction required, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running Dam Spam versions up to and including 1.0.8, especially where administrators review links or external content while authenticated.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Exploitation requires social engineering of an authenticated administrator. The practical impact is loss of pending comments, which may affect moderation, customer engagement, or auditability of submitted comments.

Researcher notes

The public description identifies missing nonce verification in settings/cleanup.php around the pending comment deletion action. References include Wordfence, GitHub source, WordPress Trac source, and a Trac changeset. Evidence supports affected versions through 1.0.8, but the bundle does not clearly name a fixed release.

Mitigation direction

  • Inventory WordPress sites for the Dam Spam plugin and installed version.
  • Prioritize sites running Dam Spam 1.0.8 or earlier.
  • Check the vendor or WordPress plugin repository for fixed versions or guidance.
  • If no fix is available, consider temporarily deactivating the plugin.
  • Remind administrators not to click untrusted links while logged into WordPress.

Validation and detection

  • Confirm whether Dam Spam is installed on each WordPress site.
  • Record the installed plugin version and compare it to 1.0.8.
  • Review vendor repository changes for nonce verification on the cleanup action.
  • Check whether pending comments were unexpectedly deleted after admin sessions.
  • Document compensating controls if the plugin remains enabled.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2026-2112 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (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:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-2112Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
webguyioDam Spam0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.