SAMO Forms <= 1.0.0 - Unauthenticated SQLi

Answer in brief

CVE-2026-80491 records a Unknown severity vulnerability in SAMO Forms <= 1.0.0 - Unauthenticated SQLi. The current sources do not mark it as known exploited. The current feed maps Unknown/SAMO Forms (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 12, 2026Updated Sep 12, 2026Source checked Sep 12, 2026First seen by HOL Sep 12, 2026Material review Sep 12, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Unknown/SAMO Forms (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Unknown/SAMO Formsgeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Unknown/SAMO Forms.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 12, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 12, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 12, 2026

Sources and claim methodology

Source referencewpscan.com

Upstream source description

The SAMO Forms WordPress plugin through 1.0.0 does not properly sanitise and escape user input before using it in SQL queries in several unauthenticated actions, allowing unauthenticated attackers to perform SQL injection attacks.

Quoted source text, attributed separately from HOL analysis.