Summary
Laravel Rest Api has a Search Validation Bypass
A validation bypass vulnerability was discovered prior to version 2.13.0, 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.
Impact:
This could lead to unauthorized data being accepted or processed by the API, depending on the context in which the validation was bypassed.
Patch:
The issue was fixed in PR #172 by ensuring that multiple rule definitions are merged correctly rather than overwritten.
Impact
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-48490? CVE-2025-48490 is a medium-severity improper input validation vulnerability in lomkit/laravel-rest-api (composer), affecting versions < 2.13.0. It is fixed in 2.13.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of lomkit/laravel-rest-api are affected by CVE-2025-48490? lomkit/laravel-rest-api (composer) versions < 2.13.0 is affected.
- Is there a fix for CVE-2025-48490? Yes. CVE-2025-48490 is fixed in 2.13.0. Upgrade to this version or later.
- Is CVE-2025-48490 exploitable, and should I be worried? Whether CVE-2025-48490 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-48490 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-48490? Upgrade
lomkit/laravel-rest-apito 2.13.0 or later.