Login Time RestrictionDrupal extension · Innoraft
CVE-2025-13982
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Drupal Login Time Restriction allows Cross Site Request Forgery.This issue affects Login Time Restriction: from 0.0.0 before 1.0.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the Drupal Login Time Restriction module allows attackers to trick authenticated users into unknowingly submitting malicious requests, potentially bypassing login time restrictions or manipulating authentication controls. The vulnerability exists in versions prior to 1.0.3.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Login Time RestrictionDrupal extension
< 1.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Login Time Restriction module is installedCheck your Drupal modules directory for the 'login_time_restriction' module. In Drupal admin, navigate to Extend or use drush pm-list --status=enabled | grep login_time_restrictionAffected if The module is present and enabled in your Drupal installation
-
Determine the installed module versionCheck the module's .info.yml file in modules/login_time_restriction/login_time_restriction.info.yml, or run: drush pm-list --format=json | grep -A5 login_time_restrictionAffected if Version is not present or is below 1.0.3
-
Verify vulnerability conditionCompare the installed version number against 1.0.3. Versions prior to 1.0.3 lack proper CSRF token validation for state-changing operations in the login time restriction settings.Affected if Installed version is less than 1.0.3 (e.g., 1.0.2, 1.0.1, 1.0.0, or any dev/alpha/beta version before 1.0.3)
You are affected if the Innoraft Login Time Restriction module is installed and its version is below 1.0.3.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.0.3
Upgrade the Login Time Restriction module to version 1.0.3 or later, which includes proper CSRF token validation for state-changing operations. If immediate upgrade is not possible, disable the module until the patch can be applied.
1.0.3
- 1. Backup your Drupal site database and files
- 2. Update the Login Time Restriction module to version 1.0.3 or later using Drupal's administrative interface (Extend > Check for updates > Update) or via Composer: composer update drupal/login_time_restriction
- 3. Clear Drupal caches after the update (Configuration > Development > Performance > Clear all caches, or using drush cr)
- 4. Verify the module is running version 1.0.3 or later at Extend > Login Time Restriction
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Login Time Restriction
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13982 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data