Which versions of PHP are affected by CVE-2026-4836?

Organizations using A vulnerability should be aware of moderate risk from CVE-2026-4836, a SQL injection vulnerability rated CVSS 5.3.

Is there a public PoC exploit available for CVE-2026-4836?

Yes, a public proof-of-concept exploit is available for CVE-2026-4836. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-4836?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Validate input sanitization for user-controlled parameters.

PHP CVE-2026-4836

Q: What is the CVSS score of CVE-2026-4836?

CVE-2026-4836 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-16081 LOW

SQL Injection (CWE-89)

2026-03-26 VulDB

GHSA-2x9h-r46q-gf7w

PHP SQLi Accounting System Code Projects

2.1

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:11 NVD

MEDIUM LOW

CVSS changed

Apr 29, 2026 - 01:11 NVD

5.3 (MEDIUM) 2.1 (LOW)

PoC Detected

Mar 30, 2026 - 13:26 vuln.today

Public exploit code

EUVD ID Assigned

Mar 26, 2026 - 02:30 euvd

EUVD-2026-16081

Analysis Generated

Mar 26, 2026 - 02:30 vuln.today

CVE Published

Mar 26, 2026 - 01:52 nvd

MEDIUM 5.3

DescriptionCVE.org

A vulnerability was detected in code-projects Accounting System 1.0. The affected element is an unknown function of the file /my_account/delete.php. Performing a manipulation of the argument cos_id results in sql injection. It is possible to initiate the attack remotely. The exploit is now public and may be used.

AnalysisAI

SQL injection in code-projects Accounting System 1.0 allows authenticated remote attackers to execute arbitrary SQL commands via the cos_id parameter in /my_account/delete.php. Public exploit code exists for this vulnerability, enabling potential unauthorized database access and manipulation. No patch is currently available.

Technical ContextAI

The vulnerability is rooted in CWE-89 (SQL Injection), a class of input validation flaw where user-supplied data is directly concatenated into SQL queries without parameterized prepared statements or proper escaping. The affected product is code-projects Accounting System (identified via CPE cpe:2.3:a:code-projects:accounting_system:*:*:*:*:*:*:*:*), a PHP-based accounting application. The vulnerability manifests in the delete.php endpoint, where the cos_id parameter is passed to an unidentified backend function that constructs dynamic SQL without input sanitization. The public exploit demonstrates time-based blind SQL injection, a technique that infers database contents by observing response delays triggered by conditional SQL sleep() commands, allowing attackers to bypass authentication checks or extract data character-by-character even when error messages are suppressed.

RemediationAI

Immediately patch code-projects Accounting System to the latest available version released by the vendor, which should include input validation and parameterized query fixes. Contact code-projects (https://code-projects.org/) directly to obtain patched releases if automatic updates are not available. As an immediate interim control pending patch deployment, restrict network access to the /my_account/delete.php endpoint to trusted internal IP ranges only, implement a Web Application Firewall (WAF) with SQL injection detection and blocking rules, and enforce strong authentication and session management to minimize the likelihood of credential compromise. Additionally, enable database query logging and alerting to detect suspicious SQL patterns or unusual data exfiltration attempts. Do not rely on obfuscation or input length limits; proper parameterized queries are the only reliable mitigation.