dbcve.org
Limit AttemptsWordPress extension · Bestwebsoft

CVE-2015-9335

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 1.1.1 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 limit-attempts plugin before 1.1.1 for WordPress has SQL injection during IP address handling.

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 confidence

SQL injection vulnerability in the limit-attempts WordPress plugin versions before 1.1.1. The vulnerability exists in the IP address handling functionality where user-supplied IP address data is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL commands.

MitigationUpdate the limit-attempts plugin to version 1.1.1 or later to remediate the SQL injection vulnerability. Given the CVSS 9.8 critical rating, this should be prioritized and applied immediately.

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
Limit AttemptsWordPress extension
Affected:< 1.1.1

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.0/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 the limit-attempts plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Limit Attempts' or 'Bestwebsoft Limit Attempts' in the plugin list
    Affected if The plugin is not found in the installed plugins list - not affected
  2. Check the installed plugin version
    In the Plugins list, click on the plugin and look for the version number displayed in the plugin details, or inspect the plugin header in /wp-content/plugins/limit-attempts/limit-attempts.php for the 'Version' tag
    Affected if Version is present and less than 1.1.1 (e.g., 1.1.0, 1.0.9, etc.) - likely affected
  3. Confirm the plugin is active
    In WordPress admin > Plugins, check if Limit Attempts shows as 'Active' under the plugin status
    Affected if Plugin is active and version is below 1.1.1 - affected and at risk
  4. Verify IP blocking/logging functionality is in use
    Check the plugin settings page (Settings > Limit Attempts) to see if IP blocking, brute force protection, or logging features are enabled
    Affected if Plugin is active, version vulnerable, and IP-related features are enabled - directly affected by the vulnerability

You are affected if the Bestwebsoft Limit Attempts plugin is installed with a version lower than 1.1.1 and the IP blocking or logging features are active.

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 1.1.1 or later
Fixed in 1.1.1
Interim mitigation

Update the limit-attempts plugin to version 1.1.1 or later to remediate the SQL injection vulnerability. Given the CVSS 9.8 critical rating, this should be prioritized and applied immediately.

Recommended fix High confidence

Limit Attempts plugin version 1.1.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Limit Attempts' plugin
  4. If the plugin shows an update available, click 'Update Now' to upgrade to version 1.1.1 or later
  5. Alternatively, navigate to Dashboard > Updates and select 'Limit Attempts' to update
  6. After updating, verify the plugin version is 1.1.1 or higher under Plugins > Installed Plugins
  7. Review the plugin settings and ensure IP address handling functionality works correctly

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

Fix this in Limit Attempts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9335 — 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-2015-9335 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