CVE-2025-64370
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 · uneditedMissing Authorization vulnerability in YOP YOP Poll yop-poll allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects YOP Poll: from n/a through <= 6.5.38.
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 confidenceYOP Poll WordPress plugin versions up to 6.5.38 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to certain functionality, enabling unauthorized actions.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 YOP Poll plugin is installedCheck for the YOP Poll plugin directory in your WordPress installation at wp-content/plugins/yop-poll/ or list installed plugins via WP admin under Plugins > Installed PluginsAffected if YOP Poll appears in the list of installed plugins
-
Determine installed YOP Poll versionOpen the main plugin file (typically yop-poll.php) and locate the version comment/constant at the top, or check the plugin version displayed in the WordPress admin plugins listAffected if The version number is 6.5.38 or lower
-
Identify accessible AJAX actionsReview plugin source files for registered AJAX handlers (search for add_action('wp_ajax_...) and add_action('wp_ajax_nopriv_...)) in the plugin directoryAffected if Any sensitive AJAX actions are registered without capability checks (no current_user_can() validation)
-
Test for missing capability checksExamine the plugin PHP files for sensitive functions (polls management, settings changes, vote recording) and verify each calls current_user_can() or similar authorization before executingAffected if Sensitive functions execute without verifying user permissions
-
Check nonce validation on actionsSearch plugin code for verify_nonce or check_admin_referer calls on AJAX action handlers and form submissionsAffected if AJAX actions or form handlers lack nonce verification before processing requests
A user is affected if YOP Poll plugin versions 6.5.38 or lower are installed and sensitive functionality lacks capability checks or nonce verification, allowing unauthorized WordPress users to perform admin-level 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 proper WordPress capability checks (current_user_can()) and nonce verification on all sensitive functions and AJAX actions within the plugin to enforce authorized access controls.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64370 — 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-64370 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