CVE-2026-0546
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 vulnerability was determined in code-projects Content Management System 1.0. This impacts an unknown function of the file search.php. This manipulation of the argument Value causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceA SQL injection vulnerability exists in the search.php file of code-projects Content Management System 1.0. The 'Value' parameter passed to an unspecified search function is not properly sanitized, allowing remote attackers to inject malicious SQL queries and potentially extract, modify, or delete database contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Code Projects CMS installationLocate the Content Management System installation directory and identify if 'search.php' exists within the application root or public web directoryAffected if search.php file is present in the Code Projects CMS installation
-
Verify CMS version is 1.0Check the application version by reviewing version files, headers, or any version identifier within the CMS installation (such as a version.php file, readme, or admin panel version display)Affected if Installed version is exactly 1.0
-
Inspect search.php for vulnerable parameter handlingOpen search.php and locate the code that handles the 'Value' parameter (typically via $_GET or $_POST). Examine whether this parameter is directly used in SQL queries without prepared statements, parameter binding, or input sanitization functions such as htmlspecialchars, mysqli_real_escape_string, or PDO::prepareAffected if The 'Value' parameter is concatenated directly into SQL queries without sanitization or prepared statements
-
Verify database connectivity is presentConfirm the application is configured with a MySQL or MariaDB database connection. Check for database configuration files (such as config.php, db.php, or similar) that establish a connection to a SQL databaseAffected if The CMS connects to a SQL database and search.php performs database queries using user input
-
Test for unauthenticated parameter exposureDetermine if the search.php endpoint is accessible without authentication. Attempt to access the search functionality directly via HTTP request to the search.php script with a test 'Value' parameterAffected if search.php is accessible without authentication and accepts the 'Value' parameter
The environment is affected if Code Projects Content Management System version 1.0 is installed, search.php exists, and the 'Value' parameter is processed in SQL queries without sanitization or prepared statements and is accessible to unauthenticated users.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) in the search.php file to ensure all user input is properly sanitized before database execution. Alternatively, implement strict input validation and escaping for the Value parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0546 — 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-0546 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