How severe is GHSA-m654-769v-qjv7?

No CVSS score has been assigned to GHSA-m654-769v-qjv7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m654-769v-qjv7?

GHSA-m654-769v-qjv7 affects the following packages: formio (npm), formio (npm). Ecosystems affected: npm.

How do I fix GHSA-m654-769v-qjv7?

Update formio to 3.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m654-769v-qjv7 is resolved across your whole dependency graph.

How do I detect GHSA-m654-769v-qjv7 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for formio. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m654-769v-qjv7 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-m654-769v-qjv7?

O3 pinpoints whether GHSA-m654-769v-qjv7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m654-769v-qjv7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m654-769v-qjv7 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-m654-769v-qjv7?

GHSA-m654-769v-qjv7 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th 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.

When was GHSA-m654-769v-qjv7 published, and has it been updated?

GHSA-m654-769v-qjv7 was published on December 10, 2025 and was last updated on December 11, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-m654-769v-qjv7

Formio improperly authorized permission elevation through specially crafted request path

Also known asCVE-2025-67718

Published

Dec 10, 2025

Updated

Dec 11, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk20th percentile+0.22%

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.

Blast Radius

2 pkgs affected

📦formio📦formio

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

Description

Security Advisory: Unauthorized permission elevation through specially crafted request path

Summary: A flaw in path handling could allow an attacker to access protected API endpoints by sending a crafted request path. This issue could result in unauthorized data disclosure under certain configurations.

Impact: In affected configurations, an unauthenticated or unauthorized request could retrieve data from endpoints that should be protected.

Affected versions: <= 3.5.6 <= 4.4.2

Fixed in: 3.5.7 4.4.3

Mitigation / Workarounds: Upgrade to 3.5.7 or later.

Disclosure timeline: Discovered 2025-05-22; fixed 2025-05-30; publicly disclosed 2025-12.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`formio`	all versions	3.5.7
📦npm	`formio`	≥ 4.0.0-rc.1&&< 4.4.3	4.4.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for formio. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update formio to 3.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m654-769v-qjv7 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 pinpoints whether GHSA-m654-769v-qjv7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m654-769v-qjv7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# Security Advisory: Unauthorized permission elevation through specially crafted request path **Summary:** A flaw in path handling could allow an attacker to access protected API endpoints by sending a crafted request path. This issue could result in unauthorized data disclosure under certain configurations. **Impact:** In affected configurations, an unauthenticated or unauthorized request could retrieve data from endpoints that should be protected. **Affected versions:** <= 3.5.6 <= 4.4.2 **Fixed in:** 3.5.7 4.4.3 **Mitigation / Workarounds:** Upgrade to 3.5.7 or later. **Disclosur

O3 Security · Impact-Aware SCA

Is GHSA-m654-769v-qjv7 in your dependencies?

O3 detects GHSA-m654-769v-qjv7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works