Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-3362

CVE-2026-3362 - Short Comment Filter Plugin

CVE-2026-3362

The Short Comment Filter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Minimum Count' settings field in all versions up to and including 2.2. This is due to insufficient input sanitization (no sanitize callback on register_setting) and missing output escaping (no esc_attr() on the echoed value in the input's value attribute). The option value is stored via update_option() and rendered unescaped in an HTML attribute context. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in the settings page that will execute whenever a user accesses that page. This is particularly impactful in WordPress multisite installations or when DISALLOW_UNFILTERED_HTML is set, where administrators are not granted the unfiltered_html capability.

CVE-2026-3362

MEDIUM CVSS 4.4 Published 2026-04-22 Updated 2026-04-22
AI Risk Moderate (47/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P4 Planned
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
Affected Components 1
Reference Links 9
AI Risk Engine Moderate (47/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-04-22 CVE published and first recorded in the threat feed.
  2. 2026-04-22 Record updated with latest vulnerability metadata.
  3. 2026-04-23 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 39 days ago

AI enriched 39 days ago (2026-04-23 01:47 UTC)

Technical Summary

The Short Comment Filter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Minimum Count' settings field in all versions up to and including 2.2. This is due to insufficient input sanitization (no sanitize callback on register_setting) and missing output escaping (no esc_attr() on the echoed value in the input's value attribute). The option value is stored via update_option() and rendered unescaped in an HTML attribute context. This makes it possible for authenticated attackers, with administrator-level access and…

Potential Impact

Severity is MEDIUM (CVSS 4.4). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 47/100 (Moderate, High) with priority P4 Planned. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Short Comment Filter PLUGIN · short-comment-filter Affected: <= 2.2 Fixed version not specified

References

Scroll to top