202CMS v10 beta SQL Injection via log_user Parameter
Published Mar 12, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
202CMS v10 beta SQL Injection via log_user Parameter
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
202CMS v10 beta contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the log_user parameter. Attackers can send crafted requests with malicious SQL statements in the log_user field to extract sensitive database information or modify database contents.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- ExploitDB-46579 ↗
- Official Product Homepage ↗
- VulnCheck Advisory: 202CMS v10 beta SQL Injection via log_user Parameter ↗
Record history
Published Mar 12, 2026 · Last refreshed Nov 3, 2026