CVE-2026-6183
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security flaw has been discovered in code-projects Simple Content Management System 1.0. Affected by this issue is some unknown functionality of the file /web/index.php. Performing a manipulation of the argument ID results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in code-projects Simple Content Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /web/index.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially exfiltrating, modifying, or deleting data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm CMS identity and versionLocate version information in the CMS installation (check README files, footer in pages, or admin panel) to identify if it is code-projects Simple Content Management System version 1.0Affected if The installed CMS is code-projects Simple Content Management System version 1.0
-
Verify vulnerable file existsCheck if the file /web/index.php exists in the web server's document rootAffected if The file /web/index.php is present in the installation
-
Inspect ID parameter handling in codeReview the source code of /web/index.php to see how the ID parameter is handled, specifically whether it is used directly in SQL queries without sanitizationAffected if The ID parameter is concatenated directly into SQL queries without sanitization or escaping
-
Check for prepared statement usageSearch the codebase (especially /web/index.php and related database files) for use of prepared statements, parameterized queries, or input validation functions when handling the ID parameterAffected if Database queries involving the ID parameter do not use mysqli_prepare, PDO prepare, or similar parameterized query methods
-
Verify database layer securityExamine the database connection/utility files to confirm whether the application uses an ORM or query builder that automatically parameterizes queries, or raw SQL execution without protectionAffected if The application uses raw SQL queries without a framework that provides automatic parameterization for the ID parameter
A user is affected if they are running code-projects Simple Content Management System version 1.0 with the vulnerable /web/index.php endpoint where the ID parameter is used in SQL queries without prepared statements or input sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement prepared statements/parameterized queries for all database interactions, especially for the ID parameter in /web/index.php. Additionally, apply input validation and output encoding to prevent injection attacks.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6183 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data