Summary
CVE-2026-80491 is an unauthenticated SQL Injection (CWE-89) vulnerability in the SAMO Forms WordPress plugin, versions through 1.0.0. The plugin fails to properly sanitize and escape user-supplied input before incorporating it into SQL queries across several unauthenticated AJAX/form actions. The flaw carries a CVSS v3.1 base score of 8.6 (High) and can be exploited remotely by any unauthenticated attacker with network access to the site.
Technical details
- Root cause: SAMO Forms does not properly sanitize or escape user-controlled input before using it in SQL query statements.
- Trigger conditions: The vulnerable code paths are reachable through several plugin actions that do not require authentication, meaning no valid WordPress account or session is needed to reach the affected queries.
- Attack vector: Network-based; an attacker sends crafted requests containing SQL injection payloads to the vulnerable, unauthenticated plugin endpoints.
- Impact: Successful exploitation allows an attacker to inject arbitrary SQL syntax into backend database queries, enabling unauthorized reading of database contents (per the CVSS vector, confidentiality impact is High, with a changed scope indicating the vulnerability can affect resources beyond the vulnerable component itself).
Affected software
- SAMO Forms WordPress plugin — all versions up to and including 1.0.0
Severity
- CVSS v3.1 Base Score: 8.6 (High)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Mitigation and recommended actions
- Immediate: As of this writing, no patched version of SAMO Forms has been released. Site owners should deactivate and remove the SAMO Forms plugin until an official fix is published by the developer.
- If no patch: As a temporary compensating control, restrict or block external network access to the affected plugin’s endpoints (e.g., via a web application firewall rule targeting the vulnerable actions), and monitor web server and database logs for anomalous or malformed input consistent with SQL injection attempts. Organizations should track the plugin’s changelog for a security release and apply it as soon as it becomes available.

