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

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

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

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

How to fix or mitigate CVE-2026-4826?

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-4826

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

CVE-2026-4826 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-16054 LOW

SQL Injection (CWE-89)

2026-03-25 VulDB

PHP SQLi Sales And Inventory System Sourcecodester

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

Apr 07, 2026 - 18:22 vuln.today

Public exploit code

EUVD ID Assigned

Mar 25, 2026 - 23:47 euvd

EUVD-2026-16054

Analysis Generated

Mar 25, 2026 - 23:47 vuln.today

CVE Published

Mar 25, 2026 - 23:35 nvd

MEDIUM 5.3

DescriptionCVE.org

A vulnerability was determined in SourceCodester Sales and Inventory System 1.0. This vulnerability affects unknown code of the file /update_stock.php of the component HTTP GET Parameter Handler. This manipulation of the argument sid causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. If you want to get best quality of vulnerability data, you may have to visit VulDB.

AnalysisAI

SQL injection in SourceCodester Sales and Inventory System 1.0 allows authenticated remote attackers to manipulate the sid parameter in /update_stock.php via HTTP GET requests, enabling unauthorized database query execution with limited confidentiality and integrity impact. Publicly available exploit code exists, and the vulnerability carries a moderate CVSS 5.3 score with low real-world exploitation probability (EPSS 0.03%, percentile 8%), indicating this is a lower-priority issue despite public disclosure.

Technical ContextAI

The vulnerability is a classic SQL injection flaw (CWE-89) in PHP code handling HTTP GET parameters. The /update_stock.php endpoint fails to properly sanitize or parameterize the sid argument before incorporating it into SQL queries, allowing attackers to inject arbitrary SQL syntax. SourceCodester Sales and Inventory System 1.0 (CPE: cpe:2.3:a:sourcecodester:sales_and_inventory_system:*:*:*:*:*:*:*:*) is a PHP-based inventory management application where the HTTP GET Parameter Handler component processes user-supplied input without adequate input validation or prepared statement usage, a fundamental secure coding failure in database-driven web applications.

RemediationAI

No vendor-released patch has been identified at time of analysis; users should contact SourceCodester directly via https://www.sourcecodester.com/ to inquire about security updates or migrate to alternative inventory management systems if updates are unavailable. As an interim mitigation, restrict access to the application to trusted internal networks only, implement Web Application Firewall (WAF) rules to block SQL injection patterns in GET parameters (specifically targeting the sid parameter), enforce strong authentication mechanisms, and apply principle of least privilege to database service accounts used by the application to minimize damage if injection succeeds. Code-level remediation requires parameterized queries or prepared statements in the /update_stock.php file to neutralize SQL injection attacks.