dbcve.org
Login SecurityDrupal extension · Login Security Project

CVE-2013-2198

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-30
Fix available
A fix is available. Upgrade to after 7.x-1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Login Security module 6.x-1.x before 6.x-1.3 and 7.x-1.x before 7.x-1.3 for Drupal allows attackers to bypass intended restrictions via a crafted username.

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 · moderate confidence

The Login Security module for Drupal versions 6.x-1.x before 6.x-1.3 and 7.x-1.x before 7.x-1.3 contains a security bypass vulnerability where attackers can circumvent intended access restrictions by using a crafted username, potentially allowing unauthorized access to the Drupal site.

MitigationUpdate the Login Security module to version 6.x-1.3 or 7.x-1.3 or later to remediate this vulnerability.

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 SecurityDrupal extension
Affected:>= 6.x-1.0, <= 6.x-1.3>= 7.x-1.0, <= 7.x-1.3= 6.x-1.0= 6.x-1.x= 7.x-1.x

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Login Security module is installed
    Check for the presence of the login_security module directory in your Drupal installation under sites/all/modules/ or sites/all/modules/contrib/. Look for a folder named 'login_security'.
    Affected if The login_security folder exists in the module directories.
  2. Determine the installed version
    Locate the login_security.info file within the login_security module folder and open it. Find the 'version' or 'core' and 'version' fields to identify the exact version number installed.
    Affected if The version field shows 6.x-1.0 through 6.x-1.3 for Drupal 6, or 7.x-1.0 through 7.x-1.3 for Drupal 7.
  3. Confirm the module is enabled
    Log in to your Drupal administration panel and navigate to the Modules page (admin/modules). Search for 'Login Security' in the list and verify whether the checkbox is checked to indicate the module is enabled.
    Affected if The Login Security module is listed and enabled (checked) in the Drupal modules administration page.
  4. Check for active username tracking features
    Review the Login Security module configuration at admin/config/people/login_security (for Drupal 7) or admin/settings/login_security (for Drupal 6). Look for options related to 'track login field' or username inspection.
    Affected if The Login Security module has active tracking or inspection features enabled for user login attempts.

Your environment is affected if the Login Security module is installed and enabled with a version between 6.x-1.0 and 6.x-1.3, or between 7.x-1.0 and 7.x-1.3.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 7.x-1.3
Interim mitigation

Update the Login Security module to version 6.x-1.3 or 7.x-1.3 or later to remediate this vulnerability.

Recommended fix High confidence

Login Security 7.x-1.4 or 6.x-1.4 (or later stable release)

  1. 1. Identify the currently installed Login Security module version in your Drupal installation (6.x or 7.x branch)
  2. 2. Navigate to the Drupal administration panel under 'Modules' or directly access the module directory
  3. 3. Download the patched version of Login Security module (7.x-1.4 or 6.x-1.4 or later) from the Drupal project page
  4. 4. Backup your current Drupal database and files before proceeding
  5. 5. Replace the existing login_security module directory with the new version
  6. 6. Run database updates if required via update.php or drush updatedb
  7. 7. Clear Drupal cache to ensure new module code is loaded
  8. 8. Verify the module is now running the patched version in the modules list
Caveat Minor - this is a security patch upgrade; review release notes for any configuration changes; always test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Login Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2198 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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