WordPress AnyComment plugin <= 0.3.6 - SQL Injection vulnerability
Priority LOW 37CWE-89Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- SQL injection
- Confidentiality · integrity · availability
- High · None · Low
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-89.
Summary
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Alexander AnyComment anycomment allows SQL Injection.This issue affects AnyComment: from n/a through <= 0.3.6.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00423 36th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-48091
- 2026-10-03 Alias added: GHSA-x74j-4vxg-f3r7
References
More Alexander vulnerabilities
- TI-2025-37606 WordPress AnyComment plugin <= 0.3.6 - Local File Inclusion vulnerability CVSS 3.1HIGH 7.5
- TI-2025-39024 WordPress AnyComment plugin <= 0.3.6 - Broken Access Control vulnerability CVSS 3.1MEDIUM 4.3
Sources
- CVE-2025-48091 · CVE Program
- CVE-2025-48091 · NVD
- FIRST EPSS
- GHSA-x74j-4vxg-f3r7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences