PatchSiren cyber security CVE debrief
CVE-2026-6182 code-projects CVE debrief
A vulnerability was identified in code-projects Simple Content Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /web/admin/login.php. Such manipulation of the argument User leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might be used. This vulnerability affects Simple Content Management System 1.0 deployments with remotely accessible /web/admin/login.php files, potentially allowing attackers to inject malicious SQL queries.
- Vendor
- code-projects
- Product
- Simple Content Management System
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-13
- Original CVE updated
- 2026-10-26
- Advisory published
- 2026-04-13
- Advisory updated
- 2026-10-26
Who should care
Defenders of Simple Content Management System 1.0 deployments, especially those with remotely accessible /web/admin/login.php files, should assess exposure and prioritize verification.
Why it matters
CVE-2026-6182 is a sql injection vulnerability in Simple Content Management System 1.0. Defenders should prioritize verifying exposure, restricting access, and monitoring for potential attacks.
- Verify exposure of Simple Content Management System 1.0
- Restrict access to the /web/admin/login.php file
- Monitor for potential sql injection attacks
Technical summary
The vulnerability is caused by manipulation of the argument User in the file /web/admin/login.php, leading to sql injection. The attack may be launched remotely. This issue affects Simple Content Management System 1.0, specifically the /web/admin/login.php file, allowing attackers to inject malicious SQL queries, which could lead to unauthorized data access or system compromise. Defenders should prioritize verifying exposure, restricting access, and monitoring for potential attacks to mitigate this vulnerability effectively.
Defensive priority
Defenders should prioritize verifying exposure of Simple Content Management System 1.0, especially if the /web/admin/login.php file is accessible remotely.
Recommended defensive actions
- Verify exposure of Simple Content Management System 1.0
- Restrict access to the /web/admin/login.php file
- Monitor for potential sql injection attacks
- Consider upgrading to a newer version of Simple Content Management System if available
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details about the vulnerability, but the vendor and affected versions are not clearly identified. The exploit is publicly available, which might be used for attacks.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-6182 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-6182
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-6182 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-6182
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://code-projects.org/
-
Source reference
Unverified legacy reference
URL: https://github.com/Xmyronn/simple-cms-sqli-login-bypass-CVE-HUNT-
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/797263
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/357105
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/357105/cti
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.