Security readout for executives and security teams
Plain-English summary
CVE-2026-0546 is a remotely reachable SQL injection in code-projects Content Management System 1.0, affecting search.php through the Value parameter. It could let an unauthenticated attacker affect database confidentiality, integrity, and availability. Public exploit information is referenced, but the provided sources do not show confirmed active exploitation.
Executive priority
Prioritize assessment for any internet-facing deployment of code-projects CMS 1.0. The risk is high because exploitation is remote and unauthenticated, with public exploit information referenced. No confirmed active exploitation is provided in the sources.
Technical view
The issue is classified as CWE-89/CWE-74. VulDB reports manipulation of the Value argument in search.php causes SQL injection. CVSS v2 is 7.5: network-accessible, low complexity, no authentication, with partial confidentiality, integrity, and availability impact. A GitHub issue is listed as an exploit reference.
Likely exposure
Exposure is likely limited to organizations running code-projects Content Management System version 1.0, especially if the CMS is internet-facing. The source bundle does not identify other affected versions or packaged distributions.
Exploitation context
The vulnerability is remotely exploitable without authentication according to the CVSS vector. Public exploit disclosure increases risk, but CISA KEV is false and the provided sources do not confirm real-world exploitation.
Researcher notes
Evidence is based mainly on CVE/VulDB records and a referenced GitHub issue. The affected function is described as unknown, and no vendor patch is named in the source bundle. Avoid assuming broader product impact beyond version 1.0.
Mitigation direction
- Inventory code-projects Content Management System deployments and confirm version 1.0 usage.
- Check code-projects and VulDB for vendor guidance or fixed releases.
- Restrict public access to the CMS where business requirements allow.
- Apply web application filtering for SQL injection patterns as a temporary control.
- If maintaining the code, review search.php database queries for parameterized input handling.
Validation and detection
- Confirm whether search.php exists in deployed CMS instances.
- Verify whether user-controlled Value input reaches database queries.
- Review web and database logs for suspicious search requests.
- Check whether the application is exposed to the internet.
- Track CVE, VulDB, and vendor pages for updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0546 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR106.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.5HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-339338 | code-projects Content Management System search.php sql injectionCVE reference · vdb-entry, technical-description
- VDB-339338 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #728924 | Code-projects Content Management System v1.0 SQL InjectionCVE reference · third-party-advisory
- https://github.com/gtxy114514/CVE/issues/1CVE reference · exploit, issue-tracking
- https://code-projects.org/CVE reference · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.