Easy Hide LoginWordPress extension · Ciphercoin
CVE-2023-31075
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 Arshid Easy Hide Login.This issue affects Easy Hide Login: from n/a through 1.0.8.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the Arshid Easy Hide Login WordPress plugin (versions through 1.0.8). The plugin fails to properly validate anti-CSRF tokens, allowing attackers to trick authenticated administrators into performing unintended actions such as disabling the login hiding protection or modifying security 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
Easy Hide LoginWordPress extension
<= 1.0.8CVSS 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.
-
Identify if Easy Hide Login plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder containing 'easy-hide-login', 'easy-hide', or check via WP admin under Plugins > Installed Plugins for a plugin named 'Easy Hide Login' or 'Ciphercoin Easy Hide Login'Affected if The plugin folder or listing is found in the WordPress plugins directory
-
Determine the installed plugin versionOpen the main plugin PHP file (usually named like easy-hide-login.php) and locate the 'Version' header in the plugin comment block, or check the version displayed in the WordPress admin plugins listAffected if The version number is 1.0.8 or lower (any version 'through 1.0.8' is affected)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the plugin status shows as 'Active', or query the wp_options table for the option 'active_plugins' containing the plugin slugAffected if The plugin shows as active in WordPress
-
Confirm the plugin handles admin security settingsAccess the plugin settings page (usually under Settings > Easy Hide Login or similar) to verify it provides options to hide login page or modify security settings - these are the state-changing operations vulnerable to CSRFAffected if The plugin settings allow toggling login hiding protection or modifying security configurations that can be changed via browser request
You are affected if the Easy Hide Login plugin version 1.0.8 or lower is installed and active on your WordPress site, and the plugin provides settings that can be modified (the CSRF flaw allows attackers to trick admins into changing these settings).
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 dataUpdate Easy Hide Login to the latest version which implements proper nonce validation and CSRF token checks on all state-changing operations; alternatively, disable the plugin until a patch is available.
Fix this in Easy 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-2023-31075 — 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-2023-31075 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