dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10938

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The UiPress lite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.5.08. This is due to missing capability checks in the 'uip_process_block_query' AJAX function. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract sensitive user data including password hashes, emails, and other user information that could be used for account takeover attacks.

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 confidence

The UiPress lite WordPress plugin fails to enforce proper authorization in its 'uip_process_block_query' AJAX function, allowing any authenticated user with subscriber-level permissions to query and retrieve sensitive user data including password hashes, emails, and other PII without elevated privileges.

MitigationUpdate UiPress lite to version 3.5.09 or later which implements proper capability checks. Alternatively, disable the plugin until an update can be applied.

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 checks

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

  1. Confirm UiPress lite plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the directory /wp-content/plugins/ for a folder named 'uipress-lite' or 'uip-lite'
    Affected if The UiPress lite plugin is found in the WordPress installation
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins and locate UiPress lite. The version number is displayed under the plugin name. Alternatively, check the main plugin file (e.g., uipress-lite.php) for the 'Version' header comment
    Affected if The version is lower than 3.5.09 (e.g., 3.5.08, 3.5.07, etc.)
  3. Verify subscriber-level accounts exist
    In WordPress admin, go to Users and review the roles assigned. Check for users with 'Subscriber' role or any role below Administrator
    Affected if There is at least one user with Subscriber role or lower privileges
  4. Confirm the AJAX endpoint is active
    Inspect the WordPress site's wp-admin/admin-ajax.php to verify the 'uip_process_block_query' action is registered. Check plugin source code for add_action('wp_ajax_uip_process_block_query', ...) calls
    Affected if The AJAX action 'uip_process_block_query' is registered and accessible to authenticated users
  5. Test for unauthorized data access (optional)
    If authorized, send an authenticated AJAX request to admin-ajax.php with action=uip_process_block_query and observe if sensitive user data (password hashes, emails) is returned without proper capability checks
    Affected if Low-privilege users can query and retrieve password hashes, emails, or other PII from the response

A WordPress site is affected if it has UiPress lite version below 3.5.09 installed AND has at least one authenticated user with subscriber-level permissions, as the vulnerable AJAX function can be exploited by any logged-in user to access sensitive user data.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update UiPress lite to version 3.5.09 or later which implements proper capability checks. Alternatively, disable the plugin until an update can be applied.

Recommended fix Moderate confidence

UiPress lite version 3.5.09 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate UiPress lite plugin
  4. Check the current version installed (should be 3.5.08 or below)
  5. Update the plugin to the latest version (3.5.09 or higher) which contains the security fix
  6. Verify the update was successful by checking the plugin version
Caveat None documented - standard plugin update within same major version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10938 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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