CVE-2025-13006
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 · uneditedThe SurveyFunnel – Survey Plugin for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.1.5 via several unprotected /wp-json/surveyfunnel/v2/ REST API endpoints. This makes it possible for unauthenticated attackers to extract sensitive data from survey responses.
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 confidenceThe SurveyFunnel WordPress plugin has unprotected REST API endpoints at /wp-json/surveyfunnel/v2/ that lack proper authentication and authorization checks, allowing any unauthenticated user to query these endpoints and extract sensitive survey response data.
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.
-
Confirm SurveyFunnel plugin is installedLog in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'SurveyFunnel' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'surveyfunnel' and read the main plugin file header for the Version field.Affected if The SurveyFunnel plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin under Plugins > Installed Plugins, find SurveyFunnel and note the version number displayed. Compare this against the fixed version 1.1.6.Affected if Installed version is lower than 1.1.6 (e.g., 1.1.5, 1.1.4, etc.)
-
Test REST API endpoint accessibilityUsing a browser or curl command, navigate to or request: https://yourdomain.com/wp-json/surveyfunnel/v2/ - examine whether the endpoint returns a valid JSON response without requiring authentication.Affected if The endpoint returns a valid JSON response (not a 401/403 error) indicating the endpoint exists and is accessible
-
Verify unauthenticated survey data accessSend a GET request to the surveyfunnel/v2/ endpoint (such as /wp-json/surveyfunnel/v2/surveys or similar survey-related routes) using curl or browser without providing any authentication credentials. Check if sensitive survey response data is returned in the response body.Affected if The API returns survey response data, participant information, or other sensitive content without requiring login credentials
The environment is affected if SurveyFunnel plugin is installed with a version lower than 1.1.6 AND the /wp-json/surveyfunnel/v2/ REST API endpoints are accessible and return sensitive data without authentication.
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 the plugin to version 1.1.6 or later which patches the vulnerability; alternatively, disable or restrict the affected REST API endpoints via server configuration or a security plugin until an update is available.
- 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-13006 — 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-13006 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