How severe is GHSA-69rh-hccr-cxrj?

No CVSS score has been assigned to GHSA-69rh-hccr-cxrj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-69rh-hccr-cxrj?

GHSA-69rh-hccr-cxrj affects the following packages: lomkit/laravel-rest-api (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-69rh-hccr-cxrj?

Update lomkit/laravel-rest-api to 2.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-69rh-hccr-cxrj is resolved across your whole dependency graph.

How do I detect GHSA-69rh-hccr-cxrj in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lomkit/laravel-rest-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-69rh-hccr-cxrj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-69rh-hccr-cxrj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-69rh-hccr-cxrj can be triaged on real exposure rather than presence alone.

Is GHSA-69rh-hccr-cxrj actively exploited in the wild?

No public exploit code has been indexed for GHSA-69rh-hccr-cxrj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-69rh-hccr-cxrj?

GHSA-69rh-hccr-cxrj has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-69rh-hccr-cxrj?

GHSA-69rh-hccr-cxrj is classified as Improper Input Validation (CWE-20), CWE-1173 (CWE-1173). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-69rh-hccr-cxrj published, and has it been updated?

GHSA-69rh-hccr-cxrj was published on May 27, 2025 and was last updated on May 30, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-69rh-hccr-cxrj: lomkit/laravel-rest-api

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-69rh-hccr-cxrj.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐘lomkit/laravel-rest-api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`lomkit/laravel-rest-api`	all versions	2.13.0`composer require lomkit/laravel-rest-api:^2.13.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lomkit/laravel-rest-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lomkit/laravel-rest-api to 2.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-69rh-hccr-cxrj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-69rh-hccr-cxrj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-69rh-hccr-cxrj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-69rh-hccr-cxrj in your dependencies?

O3 Security finds GHSA-69rh-hccr-cxrj across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-69rh-hccr-cxrj — lomkit/laravel-rest-api