CVE-2024-35773
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 WPJohnny, zerOneIT Comment Reply Email allows Cross-Site Scripting (XSS).This issue affects Comment Reply Email: from n/a through 1.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 the Comment Reply Email WordPress plugin allows attackers to craft malicious requests that inject Cross-Site Scripting (XSS) payloads. The plugin lacks proper nonce validation on form submissions, enabling authenticated users to be tricked into executing attacker-controlled JavaScript through social engineering.
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.
-
Verify Comment Reply Email plugin is installedNavigate to WordPress Admin > Plugins and locate 'Comment Reply Email' in the list of installed pluginsAffected if the plugin is installed and active
-
Identify installed plugin versionCheck the plugin header in the main plugin file (typically wp-content/plugins/comment-reply-email/main.php or similar) for the 'Version' fieldAffected if the version is lower than the patched version - compare against official WordPress plugin repository for fix version
-
Inspect form submissions for nonce fieldOpen the main plugin PHP file and search for <form> tags; verify each form includes wp_nonce_field() or a similar nonce generation functionAffected if any form handling comment replies lacks a nonce field (wp_nonce_field) before the submit button
-
Verify nonce validation in form handlersSearch the plugin code for the form action handler function and confirm it calls wp_verify_nonce, check_admin_referer, or wp_nonce_verifyAffected if the code handling form submissions does not validate a nonce before processing user input
-
Check AJAX actions for nonce validationIf the plugin uses AJAX (look for wp_ajax_ hooks), verify each hook calls wp_verify_nonce or check_admin_referer before processingAffected if any AJAX action lacks server-side nonce validation
A user is affected if the Comment Reply Email plugin is active with a version lacking nonce validation on form submissions and AJAX handlers.
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 WordPress nonces (wp_nonce_field) on all form submissions and AJAX actions, validate the nonce on the server side using check_admin_referer or wp_verify_nonce, and ensure all user-supplied data is properly sanitized before output.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35773 — 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-35773 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