dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11003

MEDIUM · 6.4 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 →
70/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 | Effortless custom dashboards, admin themes and pages plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'uip_save_ui_template' function in all versions up to, and including, 3.5.08. This makes it possible for authenticated attackers, with Subscriber-level access and above, to save templates that contain custom JavaScript.

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 has a broken access control vulnerability in the 'uip_save_ui_template' function, which lacks a capability check. This allows any authenticated user with Subscriber-level access or higher to save templates containing arbitrary JavaScript code, potentially leading to stored XSS or unauthorized template modification.

MitigationUpdate to version 3.5.09 or later which includes proper capability checks. If immediate patching is not possible, audit user roles and disable or remove subscriber-level accounts until the 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 checks

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

  1. Verify UiPress lite plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'UiPress lite' or check the plugins directory (wp-content/plugins/uipress-lite) for the plugin folder
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed version
    In WordPress admin Plugins page, find UiPress lite and view the version number. Alternatively, read the 'readme.txt' or 'uipress-lite.php' main file in the plugin directory to find the 'Version:' header
    Affected if Version is lower than 3.5.09 (vulnerable)
  3. Inspect the vulnerable function
    Examine the plugin files for the 'uip_save_ui_template' function in the includes or functions folders. Look for the function definition and verify if it contains a capability check (such as 'current_user_can' or 'wp_verify_nonce') before processing template saves
    Affected if The function exists but lacks a capability check like current_user_can() before allowing template saves
  4. Check for unauthorized template modifications
    If you have access, review the database table storing UI templates (often in wp_options or a custom table prefixed with 'uip_') for any unexpected or suspicious template entries containing JavaScript code
    Affected if Templates contain arbitrary JavaScript that was not added by an administrator

A user is affected if UiPress lite version is below 3.5.09 OR if the uip_save_ui_template function lacks a capability check, allowing any subscriber-level user to modify templates.

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 to version 3.5.09 or later which includes proper capability checks. If immediate patching is not possible, audit user roles and disable or remove subscriber-level accounts until the update can be applied.

Recommended fix Moderate confidence

3.5.09 or later

  1. Log in to the WordPress admin dashboard with administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'UiPress lite' in the plugin list
  4. Check if an update is available and update to the latest version, or manually download the latest version from wordpress.org/plugins/uipress-lite/ and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the version number is 3.5.09 or higher in the plugins list

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11003 — 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-11003 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