CVE-2025-64276
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 Ays Pro Survey Maker survey-maker allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Survey Maker: from n/a through <= 5.1.9.4.
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 confidenceSurvey Maker plugin versions up to 5.1.9.4 have a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthorized users to access functionality or data that should require elevated privileges.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Survey Maker plugin is installedCheck the WordPress plugins directory for the Survey Maker plugin files, typically located at /wp-content/plugins/survey-maker/ or via wp-cli: wp plugin list --name='survey-maker'Affected if The plugin is present in the WordPress installation
-
Check installed version numberRead the main plugin file (usually survey-maker/survey-maker.php) and look for the 'Version' header in the plugin comments, or run: grep -i 'Version:' survey-maker.phpAffected if Version is 5.1.9.4 or lower (any version up to and including 5.1.9.4)
-
Audit WordPress user roles with plugin capabilitiesAccess WordPress admin > Users > Roles or inspect user_role meta capabilities; check if any non-administrator roles have Survey Maker-specific capabilities (such as 'survey_maker_') that should be restricted to administratorsAffected if Non-administrator users or roles have elevated Survey Maker permissions that should require admin-level access
-
Review plugin access control settingsNavigate to Survey Maker settings in WordPress admin panel (usually under Survey Maker > Settings or similar) and inspect any access control, security level, or permission-related optionsAffected if Access control settings allow users below administrator level to perform privileged operations
You are affected if Survey Maker plugin version 5.1.9.4 or lower is installed AND non-administrator users have elevated permissions or the plugin's access controls are misconfigured to allow unauthorized access.
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 dataUpdate Survey Maker to version 5.1.9.5 or later to obtain the vendor patch. If immediate patching is not possible, restrict administrative access to the WordPress dashboard and audit user roles/permissions for the plugin.
- 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-2025-64276 — 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-64276 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