VulnerabilityPublished 18 Nov 2025

CVE-2025-13080: Drupal core · Unchecked Error Condition

Affects Drupal coreSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 11.2.8 : update Drupal core when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.2.8, 11.1.9, 10.5.6 +1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade drupal/core to 11.2.8, 11.1.9, 10.5.6 or 10.4.9.

Affected software

Product	Affected	Fixed in
Packagistdrupal/core`pkg:composer/drupal/core`Other threats	Affected <10.4.9 >=10.5.0 <10.5.6 >=11.0.0 <11.1.9 >=11.2.0 <11.2.8	Fixed in 10.4.9 10.5.6 11.1.9 11.2.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize upgrading Drupal core to the fixed versions: 10.4.9 or later for the 10.x branch, 10.5.6 or later for the 10.5.x branch, 11.1.9 or later for the 11.0.x branch, and 11.2.8 or later for the 11.2.x branch. If you cannot patch yet, organizations should implement strict access controls and monitor web server logs for unusual URL access patterns indicative of forceful browsing attempts. Employing web application firewalls (WAFs) with custom rules to detect and block suspicious URL manipulation can provide interim protection. Regularly auditing Drupal configurations to ensure no unintended access permissions exist is critical. Organizations should also conduct penetration testing focused on access control bypass scenarios to identify potential exposure. Maintaining up-to-date backups and incident response plans will help mitigate impact if exploitation occurs. Finally, subscribing to Drupal security advisories and threat intelligence feeds will ensure timely awareness of patches and emerging exploits.

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.

Impact

For European organizations, the impact of CVE-2025-13080 can be significant, particularly for those relying on Drupal core for public-facing websites, government portals, or critical infrastructure services. Forceful browsing could allow attackers to access restricted content or functionality, potentially disrupting service availability or exposing sensitive operational endpoints. While confidentiality and integrity are not directly affected, availability degradation could lead to service outages or degraded user experience, impacting business continuity and public trust. Organizations in sectors such as government, healthcare, finance, and media that use Drupal extensively may face operational risks and reputational damage if exploited. Additionally, attackers could leverage this vulnerability as a foothold for further attacks or reconnaissance. The medium severity rating suggests that while the threat is not critical, it requires timely attention to prevent exploitation, especially given the ease of remote exploitation without authentication.

CWE-754Improper Check for Unusual or Exceptional Conditions (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Check the results of all functions that return a value and verify that the value is expected.
Implementation
If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

drupal.org/sa-core-2025-005 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Nov 2025, 17:14 UTC

WeaknessesCWE-754

Technical details

References

Community reviews

Related threats