CVE-2025-45769

Multiple · Multiple products utilizing the php-jwt library.

A high-severity vulnerability has been identified in the php-jwt library, a common component used for user authentication in web applications.

Executive summary

A high-severity vulnerability has been identified in the php-jwt library, a common component used for user authentication in web applications. Successful exploitation could allow an unauthenticated attacker to bypass security controls and gain unauthorized access to applications and data. This poses a significant risk of account takeover and data compromise, requiring immediate attention to apply security updates.

Vulnerability

The vulnerability exists due to improper signature verification within the php-jwt v6 library. An attacker can craft a malicious JSON Web Token (JWT) with a modified payload and a manipulated cryptographic signature. The vulnerable library fails to correctly validate the integrity of this signature under specific conditions, accepting the malicious token as valid. This allows an attacker to bypass authentication mechanisms and potentially escalate privileges by forging tokens for arbitrary users, including administrators.

Business impact

This vulnerability is rated as High severity with a CVSS score of 7.3. Exploitation could lead to a complete compromise of application-level security. The primary business impact includes unauthorized access to sensitive company or customer data, potential data breaches, and fraudulent transactions performed by an attacker impersonating a legitimate user. These outcomes can result in significant financial loss, reputational damage, and potential regulatory penalties for non-compliance with data protection standards.

Remediation

Immediate Action: Organizations must immediately identify all applications and systems that use the vulnerable php-jwt v6 library. Apply the security updates or patches provided by the respective software vendors as the primary remediation step. After patching, review application and server access logs for any signs of past or ongoing exploitation attempts.

Proactive Monitoring: Implement enhanced monitoring on authentication endpoints. Security teams should look for anomalies in authentication logs, such as malformed JWTs, a sudden spike in token validation errors, or successful authentications from unusual IP addresses or geolocations. Configure Web Application Firewalls (WAFs) to detect and block requests containing known malicious JWT patterns.

Compensating Controls: If immediate patching is not feasible, implement a WAF rule to block JWTs that exhibit characteristics of the exploit. Consider adding a secondary token validation layer at an API gateway or load balancer that uses a non-vulnerable library to re-verify token signatures before the request reaches the affected application. Restrict access to critical application endpoints to trusted internal networks only.

Exploitation status

Public Exploit Available: false

Analyst recommendation

Given the high-severity rating (CVSS 7.3) and the critical function of the affected component (authentication), this vulnerability presents a significant risk to the organization. While it is not currently listed in the CISA KEV catalog and no public exploits are available, the potential for authentication bypass warrants immediate action. We strongly recommend that organizations prioritize identifying all instances of the vulnerable php-jwt library and applying the necessary security patches without delay to prevent potential compromise.