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

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

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

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

How to fix or mitigate CVE-2026-4777?

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

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

CVE-2026-4777 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-15026 LOW

SQL Injection (CWE-89)

2026-03-24 VulDB

GHSA-9jvv-qw4v-hm39

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 08, 2026 - 18:53 vuln.today

Public exploit code

EUVD ID Assigned

Mar 24, 2026 - 22:01 euvd

EUVD-2026-15026

Analysis Generated

Mar 24, 2026 - 22:01 vuln.today

CVE Published

Mar 24, 2026 - 21:42 nvd

MEDIUM 5.3

DescriptionCVE.org

A security flaw has been discovered in SourceCodester Sales and Inventory System 1.0. This affects an unknown part of the file view_supplier.php of the component POST Parameter Handler. The manipulation of the argument searchtxt results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.

AnalysisAI

SQL injection in SourceCodester Sales and Inventory System 1.0's view_supplier.php POST parameter handler allows authenticated attackers to execute arbitrary SQL queries through the searchtxt parameter. Public exploit code exists for this vulnerability, increasing the risk of active exploitation. The vulnerability affects PHP-based installations and currently lacks an available patch.

Technical ContextAI

The vulnerability is a classic SQL injection (CWE-89) flaw in a PHP-based web application. The view_supplier.php component processes POST parameters without proper input validation or parameterized query usage, allowing attackers to manipulate the 'searchtxt' argument to alter SQL query logic. The affected technology stack involves PHP server-side processing with likely MySQL or similar relational database backend. According to CPE data (cpe:2.3:a:sourcecodester:sales_and_inventory_system), this is a web-based inventory management application. The root cause is insufficient input sanitization before SQL query construction, a well-documented and preventable class of vulnerability.

RemediationAI

The primary remediation is to contact SourceCodester for security updates or upgrade to a patched version if available via https://www.sourcecodester.com/. As an immediate mitigation, implement parameterized queries (prepared statements) in the view_supplier.php POST parameter handler to eliminate SQL injection; sanitize all user input (searchtxt parameter) using whitelisting and escaping appropriate to the database backend. Restrict database account privileges to the minimum required for the application function, implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns in the searchtxt parameter, and enforce strong authentication and access controls to reduce the likelihood of unauthorized authenticated access. Monitor application logs for suspicious SQL patterns and consider running the application in a database transaction isolation mode that limits data exposure.