Survey MakerWordPress extension · Ays Pro
CVE-2025-32275
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 · uneditedAuthentication Bypass by Spoofing vulnerability in Ays Pro Survey Maker survey-maker allows Identity Spoofing.This issue affects Survey Maker: from n/a through <= 5.1.6.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 · moderate confidenceThe vulnerability is an Authentication Bypass by Spoofing in Ays Pro Survey Maker plugin that allows attackers to impersonate other users by circumventing identity verification mechanisms. This identity spoofing flaw enables unauthorized access to the survey platform by falsifying authentication credentials or session data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Survey MakerWordPress extension
<= 5.1.5.4CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Locate Ays Pro Survey Maker plugin installationCheck your WordPress installation at wp-content/plugins/ for a folder named 'ays-survey-maker' or 'ays-pro-survey-maker', or access the Plugins section in WordPress admin dashboardAffected if The plugin folder or listing shows Ays Pro Survey Maker is present
-
Determine installed plugin versionOpen the main plugin PHP file (typically ays-survey-maker.php or similar in the plugin folder) and locate the 'Version' header comment, or view the version in WordPress admin under Plugins > Installed PluginsAffected if The reported version number is 5.1.5.4 or any lower version number
-
Confirm plugin is activeIn WordPress admin, navigate to Plugins > Installed Plugins and verify whether Ays Pro Survey Maker is currently activatedAffected if The plugin shows as 'Active' status in the plugin list
You are affected if Ays Pro Survey Maker is installed and active with version 5.1.5.4 or lower on your WordPress site.
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.
dbcve · scopedApply the latest vendor patch for Survey Maker (version > 5.1.6.3) when available, and implement additional authentication safeguards such as multi-factor authentication and proper session token validation.
Survey Maker version 5.1.6.4 or later
- 1. Log in to the WordPress admin dashboard where the Survey Maker plugin is installed.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate the 'Survey Maker' plugin in the list.
- 4. If an update is available, click 'Update Now' to upgrade to the latest version.
- 5. Alternatively, download the latest version from the WordPress Plugin Repository or from Ays Pro's official website.
- 6. After updating, verify the plugin version in Plugins > Installed Plugins to confirm the upgrade was successful.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Survey Maker
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32275 — 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-32275 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