How severe is GHSA-83v7-c2cf-p9c2?

No CVSS score has been assigned to GHSA-83v7-c2cf-p9c2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-83v7-c2cf-p9c2?

GHSA-83v7-c2cf-p9c2 affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-83v7-c2cf-p9c2?

Update drupal/core to 10.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-83v7-c2cf-p9c2 is resolved across your whole dependency graph.

How do I detect GHSA-83v7-c2cf-p9c2 in my Packagist dependencies?

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

How do I mitigate GHSA-83v7-c2cf-p9c2 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.

Is GHSA-83v7-c2cf-p9c2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-83v7-c2cf-p9c2 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-83v7-c2cf-p9c2?

GHSA-83v7-c2cf-p9c2 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th 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-83v7-c2cf-p9c2?

GHSA-83v7-c2cf-p9c2 is classified as CWE-754 (CWE-754). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-83v7-c2cf-p9c2 published, and has it been updated?

GHSA-83v7-c2cf-p9c2 was published on November 18, 2025 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Drupal core allows Forceful BrowsingGHSA-83v7-c2cf-p9c2

GHSA-83v7-c2cf-p9c2 is a CWE-754 vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.

Also known asBIT-drupal-2025-13080CVE-2025-13080DRUPAL-CORE-2025-005

Published

Nov 18, 2025

Updated

Dec 10, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-83v7-c2cf-p9c2.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core

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

Improper Check for Unusual or Exceptional Conditions vulnerability in Drupal Drupal core allows Forceful Browsing. This issue affects Drupal core: from 8.0.0 before 10.4.9, from 10.5.0 before 10.5.6, from 11.0.0 before 11.1.9, from 11.2.0 before 11.2.8.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.0.0&&< 10.4.9	10.4.9`composer require drupal/core:^10.4.9`
🐘Packagist	`drupal/core`	≥ 10.5.0&&< 10.5.6	10.5.6`composer require drupal/core:^10.5.6`
🐘Packagist	`drupal/core`	≥ 11.0.0&&< 11.1.9	11.1.9`composer require drupal/core:^11.1.9`
🐘Packagist	`drupal/core`	≥ 11.2.0&&< 11.2.8	11.2.8`composer require drupal/core:^11.2.8`

Affected Products

1 product · 4 configurations

Application

drupaldrupal

≥ 11.2.0 && < 11.2.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 10.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-83v7-c2cf-p9c2 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-83v7-c2cf-p9c2 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works