Erident Custom Login And DashboardWordPress extension · Erident Custom Login And Dashboard Project
CVE-2015-9322
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 erident-custom-login-and-dashboard plugin before 3.5 for WordPress has CSRF.
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 erident-custom-login-and-dashboard WordPress plugin before version 3.5 is vulnerable to Cross-Site Request Forgery (CSRF), allowing attackers to trick authenticated administrators into performing unintended actions by submitting malicious requests.
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
Erident Custom Login And DashboardWordPress extension
< 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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 the plugin filesCheck your WordPress installation's wp-content/plugins/ directory for the 'erident-custom-login-and-dashboard' folder, or look in the WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists and the plugin is installed
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins, find Erident Custom Login And Dashboard, and note the version number displayed beneath the plugin nameAffected if The version number is less than 3.5 (for example, 3.4, 3.3, etc.)
-
Inspect form handling for nonce verificationExamine the main plugin PHP file (typically erident-custom-login-and-dashboard.php) and look for form submission handlers and AJAX action hooks. Search for occurrences of 'wp_verify_nonce' or 'check_admin_referer' within these handler functionsAffected if Form handlers or AJAX endpoints lack nonce verification code, meaning requests can be forged
-
Verify nonce implementation across all submission pointsReview all PHP files in the plugin folder for form tags and JavaScript AJAX calls. Confirm each form submission and AJAX request includes a nonce field or parameter that gets verified server-side before processingAffected if Any form or AJAX action processes requests without validating a nonce token
You are affected if the Erident Custom Login And Dashboard plugin is installed with a version lower than 3.5 and the plugin's forms or AJAX handlers do not implement WordPress nonce verification.
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 data3.5
Update to version 3.5 or later which includes CSRF protection. Implement WordPress nonces on all form submissions and AJAX requests within the plugin.
Fix this in Erident Custom Login And Dashboard
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9322 — 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-9322 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