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

CVE-2026-4596 is a low-severity vulnerability in A vulnerability involving cross-site scripting (CVSS 3.5).

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

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

How to fix or mitigate CVE-2026-4596?

During next maintenance window: Apply vendor patches when convenient. Verify cross-site scripting controls are in place.

PHP CVE-2026-4596

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

CVE-2026-4596 has a CVSS 4.0 base score of 2.0 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/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-14527 LOW

Cross-site Scripting (XSS) (CWE-79)

2026-03-23 VulDB

PHP XSS Lawyer Management System Projectworlds

2.0

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

2.0 LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/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

Scope

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:11 NVD

MEDIUM LOW

CVSS changed

Apr 29, 2026 - 01:11 NVD

5.1 (MEDIUM) 2.0 (LOW)

PoC Detected

Apr 10, 2026 - 20:35 vuln.today

Public exploit code

EUVD ID Assigned

Mar 23, 2026 - 19:45 euvd

EUVD-2026-14527

Analysis Generated

Mar 23, 2026 - 19:45 vuln.today

CVE Published

Mar 23, 2026 - 19:20 nvd

MEDIUM 5.1

DescriptionCVE.org

A vulnerability was identified in projectworlds Lawyer Management System 1.0. This issue affects some unknown processing of the file /lawyers.php. The manipulation of the argument first_Name leads to cross site scripting. The attack may be initiated remotely. The exploit is publicly available and might be used.

AnalysisAI

A stored or reflected cross-site scripting (XSS) vulnerability exists in projectworlds Lawyer Management System version 1.0, specifically in the /lawyers.php file where the first_Name parameter is inadequately sanitized. An authenticated attacker can inject malicious JavaScript that executes in the context of other users' browsers, potentially stealing session tokens or performing unauthorized actions. A public proof-of-concept exploit is available, and exploitation requires only low complexity with user interaction (UI:R), though the attack vector is network-accessible and does not require high privileges.

Technical ContextAI

The vulnerability stems from CWE-79 (Improper Neutralization of Input During Web Page Generation), a classic input validation weakness in web applications. The affected software is projectworlds Lawyer Management System (CPE: cpe:2.3:a:projectworlds:lawyer_management_system:*:*:*:*:*:*:*:*), a PHP-based application. The root cause is the failure to properly encode or validate user-supplied input in the first_Name parameter before reflecting it back in the HTML response of /lawyers.php. Since the application is PHP-based and processes user input without sanitization (likely missing htmlspecialchars() or equivalent output encoding), an attacker can inject script tags or event handlers that execute client-side in the victim's browser when the page is rendered.

RemediationAI

The primary remediation is to upgrade projectworlds Lawyer Management System to a patched version when available; check the vendor's website and VulDB (https://vuldb.com/?id.352434) for patch availability and timeline. In the interim, implement input validation and output encoding in the /lawyers.php file: ensure the first_Name parameter is validated against a whitelist (alphanumeric and safe characters only) and encoded using htmlspecialchars($input, ENT_QUOTES, 'UTF-8') before rendering in HTML context. Additionally, enforce Content Security Policy (CSP) headers to restrict inline script execution and mitigate XSS impact. Limit access to the /lawyers.php endpoint to trusted internal networks if possible, and enforce HTTPS with secure session cookies (HttpOnly, Secure flags) to protect authenticated sessions from token theft.