Missing AuthorizationWeakness · CWE-862

CVE-2025-10694

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-25

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The User Feedback – Create Interactive Feedback Form, User Surveys, and Polls in Seconds plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the `maybe_load_onboarding_wizard` function in all versions up to, and including, 1.8.0. This makes it possible for unauthenticated attackers to access the onboarding wizard page and view configuration information including the administrator email address.

Technical summary

dbcve analysis · high confidence

The User Feedback WordPress plugin has a missing capability check on the `maybe_load_onboarding_wizard` function in versions up to 1.8.0. This allows unauthenticated attackers to directly access the onboarding wizard page without authentication, exposing sensitive configuration information including the administrator email address.

MitigationUpdate the plugin to version 1.8.1 or later which contains the capability check fix. If an update is unavailable, consider disabling the plugin until a patched version is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify User Feedback plugin is installed

In WordPress admin, go to Plugins > Installed Plugins and look for 'User Feedback' plugin, or check for the /wp-content/plugins/user-feedback/ directory on the file system

Affected if The plugin appears in the list or directory exists on the server
Determine installed plugin version

In the Plugins list view, note the version number displayed under the User Feedback plugin name, or open the main plugin file (user-feedback.php) and locate the 'Version:' header comment

Affected if The version is 1.8.0 or lower (1.8.0, 1.7.x, 1.6.x, etc.)
Test unauthenticated onboarding wizard access

Open a browser in incognito/private mode and directly navigate to the onboarding wizard URL (commonly /wp-admin/admin.php?page=user-feedback-onboarding or similar path ending with 'onboarding'), without logging in

Affected if The wizard page loads and displays configuration forms or the administrator email address without requiring authentication credentials
Inspect the maybe_load_onboarding_wizard function

Examine the plugin source code file containing the maybe_load_onboarding_wizard function; search for a capability check such as current_user_can() or wp_verify_nonce() before the wizard logic executes

Affected if No capability or authorization check is found before the onboarding wizard code runs

The environment is affected if the User Feedback plugin version is 1.8.0 or lower AND the onboarding wizard is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the plugin to version 1.8.1 or later which contains the capability check fix. If an update is unavailable, consider disabling the plugin until a patched version is released.

Recommended fix Moderate confidence

Latest version available on wordpress.org (version higher than 1.8.0)

Log in to WordPress admin dashboard
Navigate to Plugins > Installed Plugins
Locate 'User Feedback – Create Interactive Feedback Form, User Surveys, and Polls in Seconds'
Check current installed version (should be 1.8.0 or lower if vulnerable)
Update the plugin to the latest available version via 'Update Now' button or upload newer version from wordpress.org

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-10694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10694 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-10694?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-10694 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References