LoginizerWordPress extension
CVE-2017-12650
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 · uneditedSQL Injection exists in the Loginizer plugin before 1.3.6 for WordPress via the X-Forwarded-For HTTP header.
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 confidenceSQL injection vulnerability in the Loginizer WordPress plugin versions prior to 1.3.6 allows remote attackers to inject malicious SQL code through the X-Forwarded-For HTTP header, which is improperly sanitized when recording failed login attempts.
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
LoginizerWordPress extension
<= 1.3.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Loginizer plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find Loginizer, then note the version number displayed. Alternatively, check the plugin file /wp-content/plugins/loginizer/loginizer.php for the 'Version' header comment.Affected if The displayed version is 1.3.5 or lower.
-
Verify Loginizer is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the Loginizer plugin shows as 'Active'.Affected if The plugin is active and the version is 1.3.5 or lower.
-
Confirm failed login logging is enabledIn WordPress admin, navigate to Loginizer Settings > Failed Login Logs. Check if logging is enabled or if any logs exist.Affected if Failed login logging is enabled or logs are present, as the vulnerability exploits how failed attempts are recorded.
-
Check for reverse proxy headers in useInspect HTTP request headers on your WordPress site, specifically looking for X-Forwarded-For headers being passed. Check server configuration (Apache/Nginx) for use of proxy headers.Affected if X-Forwarded-For headers are being processed by the server, as this is the attack vector for SQL injection.
User is affected if Loginizer plugin version 1.3.5 or lower is installed and active on WordPress, with failed login logging enabled and the site processing X-Forwarded-For headers.
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 · scopedUpdate the Loginizer plugin to version 1.3.6 or later to apply the vendor fix for this SQL injection vulnerability.
Loginizer 1.3.6
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Find the Loginizer plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to version 1.3.6
- 5. Alternatively, download Loginizer version 1.3.6 from the official WordPress plugin repository (sv.wordpress.org)
- 6. Deactivate the current Loginizer plugin
- 7. Upload and install the new version
- 8. Reactivate the plugin
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Loginizer
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12650 — 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-2017-12650 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