CVE-2024-51634
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 a.ankit Webriti Custom Login webriti-custom-login-page allows Reflected XSS.This issue affects Webriti Custom Login: from n/a through <= 0.3.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Webriti Custom Login plugin version <= 0.3 allows attackers to trick authenticated administrators into performing unintended actions that result in Reflected XSS injection. The lack of CSRF token validation enables malicious requests to be crafted on behalf of victims.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 Webriti Custom Login plugin is installedAccess your WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Webriti Custom Login' in the list. Note the version number displayed.Affected if The plugin appears in the installed plugins list with a version number of 0.3 or lower
-
Confirm the exact version numberClick on the plugin name or view details to read the version field directly. Compare it against the affected range: version 0.3 and below.Affected if The installed version is 0.3 or any version lower than 0.3
-
Inspect admin action forms for CSRF protectionAccess the plugin settings page in the WordPress admin panel. View the page source (right-click > View Page Source) or use browser developer tools to examine HTML forms that perform state-changing actions (such as saving settings, updating options, or modifying plugin configuration).Affected if Forms submitting to admin-ajax.php or other admin action endpoints lack a nonce field (typically named _wpnonce or similar) or do not verify nonce tokens on submission
-
Check for nonce verification in plugin code (if access to source)If you have file system access, locate the plugin directory (wp-content/plugins/custom-login or similar). Search PHP files for presence of wp_verify_nonce, check_admin_referer, or nonce verification calls on admin action handlers.Affected if Admin action handlers do not contain nonce verification functions, or verification is missing entirely from the code handling form submissions
You are affected if the Webriti Custom Login plugin is installed with version 0.3 or lower AND admin forms lack CSRF token validation.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing admin actions and apply proper output encoding/escaping to prevent reflected XSS. Update to a patched version when available.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51634 — 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-2024-51634 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