CVE-2025-13982VulnerabilityPublished 28 Jan 2026

CVE-2025-13982: Drupal Login Time Restriction · Cross-Site Request Forgery (CSRF)

Affects Drupal Login Time RestrictionSource CVE Database V5

Not known to be exploited · CVSS 8.1 High : upgrade to 1.0.3 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.1High

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.3

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

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

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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
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 2026-10-26.

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 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 Login Time Restriction to 1.0.3.

Affected software

Product	Affected	Fixed in
DrupalLogin Time Restriction	Affected <1.0.3	Fixed in 1.0.3

AI-suggested

European organizations should take the following specific mitigation steps: 1) Immediately verify the version of the Drupal Login Time Restriction module in use and plan to upgrade to version 1.0.3 or later as soon as it becomes available. 2) Until a patch is applied, implement additional CSRF protections such as verifying anti-CSRF tokens on all state-changing requests related to login time restrictions. 3) Restrict access to administrative interfaces and sensitive configuration endpoints using network-level controls or web application firewalls (WAF) with custom rules to detect and block suspicious CSRF-like requests. 4) Educate users and administrators about the risks of CSRF and encourage cautious behavior regarding unsolicited links or emails. 5) Monitor web server and application logs for unusual POST requests or changes to login time policies that could indicate exploitation attempts. 6) Conduct regular security audits and penetration testing focusing on authentication and session management modules. 7) Coordinate with Drupal security advisories and subscribe to vulnerability notifications to stay informed about patches and exploit developments. 8) Consider implementing multi-factor authentication (MFA) to reduce the impact of compromised login controls.

Description

CVE-2025-13982 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability affecting the Drupal Login Time Restriction module versions before 1.0.3. This vulnerability allows an attacker to trick authenticated users into executing unwanted actions related to login time restrictions without their consent. Exploitation requires user interaction but no privileges or authentication are needed, and it can result in high confidentiality and integrity impacts. Although no known exploits are currently in the wild, the vulnerability poses a significant risk to Drupal sites using this module. European organizations relying on Drupal for web content management could face unauthorized changes to login policies, potentially leading to unauthorized access or denial of legitimate access. Mitigation involves promptly updating the module to version 1.0.3 or later once available, implementing anti-CSRF tokens, and monitoring for suspicious activity.

Impact

For European organizations, the impact of CVE-2025-13982 can be significant, especially for those using Drupal as their primary content management system. Unauthorized modification of login time restrictions could allow attackers to circumvent security policies, potentially gaining unauthorized access during restricted periods or locking out legitimate users, disrupting business operations. This could lead to data breaches compromising sensitive personal or corporate data, violating GDPR and other data protection regulations, resulting in legal and financial penalties. The integrity of authentication controls is compromised, increasing the risk of further exploitation or lateral movement within networks. Public sector, financial institutions, healthcare providers, and large enterprises in Europe that rely on Drupal for web portals or intranet services are particularly at risk. The vulnerability could also be leveraged in targeted attacks against critical infrastructure or government websites, amplifying the potential impact. Although no exploits are currently known, the ease of exploitation and high impact warrant immediate attention to prevent future incidents.

Summary

CVE-2025-13982 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Drupal Login Time Restriction module, specifically affecting versions prior to 1.0.3. CSRF vulnerabilities allow attackers to induce authenticated users to perform actions they did not intend by exploiting the trust a web application places in the user's browser. In this case, the vulnerability permits an attacker to manipulate login time restrictions by sending crafted requests that the victim's browser executes unknowingly. The vulnerability requires no privileges (PR:N) and can be exploited remotely over the network (AV:N) with low attack complexity (AC:L), but does require user interaction (UI:R), such as clicking a malicious link or visiting a malicious website. The impact on confidentiality and integrity is high (C:H/I:H), as unauthorized changes to login time restrictions could allow attackers to bypass access controls or lock out legitimate users. Availability is not impacted (A:N). The vulnerability affects the Login Time Restriction module, which is used to enforce time-based login policies in Drupal environments. Although no public exploits are currently known, the high CVSS score of 8.1 reflects the serious risk posed by this vulnerability. The issue was reserved in December 2025 and published in January 2026, indicating recent discovery and disclosure. No official patches or updates were linked at the time of reporting, but upgrading to version 1.0.3 or later is expected to resolve the issue. The vulnerability is tracked under CWE-352, a common web security weakness related to CSRF attacks.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

drupal.org/sa-contrib-2025-120 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Feb 2026, 08:50 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats