Wps Hide LoginWordPress extension · Wpserveur
CVE-2015-9498
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 · uneditedThe wps-hide-login plugin before 1.1 for WordPress has CSRF that affects saving an option value.
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 confidenceThe wps-hide-login WordPress plugin before version 1.1 is vulnerable to Cross-Site Request Forgery (CSRF) that allows attackers to forge administrator requests to save or modify plugin option values. The lack of anti-CSRF tokens in the options form and handler enables authenticated administrators to be tricked into unknowingly changing settings.
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
Wps Hide LoginWordPress extension
< 1.1CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate wps-hide-login plugin installationCheck the wp-content/plugins directory for the wps-hide-login folder, or query the WordPress database plugins table for the plugin entry.Affected if The plugin folder or database entry does not exist, meaning the plugin is not installed.
-
Confirm plugin version numberOpen the main plugin PHP file (typically wps-hide-login/wps-hide-login.php) and locate the Version header in the plugin comment block, or check the WordPress plugins admin page for the installed version.Affected if The displayed version is below 1.1 (for example, 1.0.x or earlier).
-
Verify plugin is activeCheck the WordPress admin under Plugins > Installed Plugins to confirm wps-hide-login is activated, or query the wp_options table for the active_plugins option.Affected if The plugin is installed but not activated; CSRF requires an active configuration form to be exploitable.
-
Inspect options form for nonce fieldExamine the plugin file that renders the settings form (commonly in admin settings pages) and search for a wp_nonce_field() call or similar nonce verification within the form output.Affected if The form markup contains no _wpnonce or similar hidden token field, indicating missing CSRF protection.
-
Inspect options handler for nonce verificationReview the PHP code that processes the form submission (the handler function) and look for wp_verify_nonce() or check_admin_referer() calls before saving options.Affected if The handler lacks nonce verification logic, meaning any request can modify settings without validation.
If the installed wps-hide-login version is below 1.1 and the plugin is active with the settings form lacking nonce verification, the environment is affected by this CSRF vulnerability.
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.
From vendor data1.1
Update wps-hide-login plugin to version 1.1 or later which implements proper nonce verification. As an interim measure, ensure administrators are not browsing untrusted sites while authenticated and consider implementing additional request validation.
Fix this in Wps Hide Login
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9498 — 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-2015-9498 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