CVE-2026-8126: SourceCodester Comment System · SQL Injection
Affects SourceCodester Comment SystemSource CVE Database V5
Public exploit available · CVSS 6.9 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SourceCodesterComment System | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, users should consider implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the post_comment.php endpoint. Input validation and sanitization on the 'Name' parameter should be enforced as a temporary mitigation.
Description
CVE-2026-8126 is a medium severity SQL injection vulnerability in SourceCodester Comment System version 1.0. The flaw exists in the post_comment.php file where manipulation of the 'Name' argument allows remote attackers to perform SQL injection. There is no official patch or remediation guidance available at this time. Exploit code has been published, but no known exploits in the wild have been reported. The vulnerability allows an attacker to potentially interfere with the backend database through crafted input.