Laravel Rest Api has a Search Validation Bypass

published 2025-05-27 17 mo ago modified 2026-06-17 4 mo ago also GHSA-69rh-hccr-cxrj , EUVD-2025-16349

cvss: 6.6; version 4.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits: 0; none known

Laravel Rest Api is an API generator. Prior to version 2.13.0, a validation bypass vulnerability was discovered where multiple validations defined for the same attribute could be silently overridden. Due to how the framework merged validation rules across multiple contexts (such as index, store, and update actions), malicious actors could exploit this behavior by crafting requests that bypass expected validation rules, potentially injecting unexpected or dangerous parameters into the application. This could lead to unauthorized data being accepted or processed by the API, depending on the context in which the validation was bypassed. This issue has been patched in version 2.13.0.

Patch / fix

fixed in 1 links 2

packagist lomkit/laravel-rest-api 2.13.0

github.com/Lomkit/laravel-rest-api@88b1458 commit
github.com/Lomkit/laravel-rest-api#172 pull request

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 17 mo ago (2025-05-30)

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	4.0	6.6	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
CNA	4.0	6.6	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/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

Affected packages

ecosystem	package	affected	fixed in
packagist	lomkit/laravel-rest-api	<2.13.0	2.13.0

Affected products

Lomkit laravel-rest-api

Classification

Weakness

CWE-20 Improper Input Validation
CWE-1173 Improper Use of Validation Framework

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary