Security readout for executives and security teams
Plain-English summary
CVE-2026-0567 is a SQL injection in code-projects Content Management System 1.0. A remote, unauthenticated attacker may manipulate the ID parameter in /pages.php to affect database confidentiality, integrity, and availability. Public exploit information exists, but the provided sources do not show confirmed active exploitation or a vendor fix.
Executive priority
Treat as a high-priority exposure if this CMS is in use, particularly on public websites. Public exploit availability raises urgency. If the product is not deployed, business risk is minimal beyond confirming inventory.
Technical view
The issue is reported in an unknown function handling /pages.php, where the ID argument is not safely handled, causing SQL injection. VulDB rates it CVSS 2.0 7.5 with network access, low complexity, and no authentication required. Listed CWEs are CWE-74 and CWE-89.
Likely exposure
Exposure is likely limited to organizations running code-projects Content Management System version 1.0, especially internet-facing deployments exposing /pages.php. The CPE in the source uses a wildcard version, but the narrative specifically names version 1.0.
Exploitation context
The source bundle states the exploit is public and may be used, and includes a GitHub issue tagged as exploit. The CVE is not listed as KEV in the provided data, so active exploitation is not confirmed here.
Researcher notes
Evidence is sparse and appears driven by VulDB and a public GitHub issue. No vendor patch, fixed version, or active exploitation confirmation is present in the provided sources. Validate affected code paths carefully and avoid assuming other code-projects products are impacted.
Mitigation direction
- Identify any code-projects Content Management System 1.0 deployments.
- Restrict public access to affected CMS instances where feasible.
- Check code-projects and VulDB guidance for patches or vendor remediation.
- Apply vendor updates if and when available.
- Use database least privilege for the CMS application account.
- Review web application firewall rules for SQL injection detection.
Validation and detection
- Inventory internet-facing sites for code-projects Content Management System 1.0.
- Confirm whether /pages.php is reachable externally.
- Review web logs for unusual requests targeting the ID parameter.
- Check application code or vendor version metadata for affected version.
- Verify database account privileges used by the CMS.
- Monitor referenced advisories for updated fix information.
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-0567 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-339379 | code-projects Content Management System pages.php sql injectionCVE reference · vdb-entry, technical-description
- VDB-339379 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #729229 | Code-projects Content Management System v1.0 SQL injectionCVE reference · third-party-advisory
- https://github.com/Limingqian123/CVE/issues/14CVE 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.