CVE-2025-62134
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 WP Life Contact Form Widget new-contact-form-widget allows Cross Site Request Forgery.This issue affects Contact Form Widget: from n/a through <= 1.5.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the A WP Life Contact Form Widget plugin (new-contact-form-widget) versions up to and including 1.5.1. The plugin fails to properly validate the origin of requests, allowing authenticated attackers to trick administrators into performing unintended actions like modifying contact form settings or submitting forms on their behalf.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 the plugin is installedCheck the WordPress plugins directory for the 'new-contact-form-widget' or 'A WP Life Contact Form Widget' plugin folder, typically located at wp-content/plugins/Affected if The plugin folder exists in the WordPress installation
-
Determine the installed versionOpen the main plugin file (usually new-contact-form-widget.php) and locate the Version header in the plugin comment block, or check in WordPress admin under Plugins > Installed PluginsAffected if The reported version is 1.5.1 or any version below 1.5.1 (the plugin lacks the fix in all versions up to 1.5.1)
-
Check for nonce validation in form submissionsExamine the plugin's PHP files for the presence of 'wp_verify_nonce', 'check_ajax_referer', or 'check_admin_referer' function calls when processing form submissions or AJAX requestsAffected if The plugin code does not validate nonces on state-changing operations (form submissions, settings changes, AJAX actions)
-
Verify HTTP Referer header validationReview the plugin's PHP code to see if $_SERVER['HTTP_REFERER'] or $_SERVER['REQUEST_URI'] is checked to validate request origin before processing any admin actionsAffected if The plugin does not validate the HTTP Referer header to confirm requests originate from the legitimate site
You are affected if the A WP Life Contact Form Widget plugin is installed with version 1.5.1 or below and the plugin code lacks nonce verification and Referer header validation on form processing and admin actions.
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 (nonce validation) on all state-changing operations within the plugin, including form submissions and AJAX actions. Additionally, validate the HTTP Referer header to ensure requests originate from legitimate sources.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62134 — 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-2025-62134 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