dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-3053

HIGH · 8.8 CVSS v3.1 Published 2025-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Remote Code Execution in all versions up to, and including, 3.5.07 via the uip_process_form_input() function. This is due to the function taking user supplied inputs to execute arbitrary functions with arbitrary data, and does not have any sort of capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary code on the server.

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 contains an RCE vulnerability in the uip_process_form_input() function in versions up to 3.5.07. This function accepts user-supplied input and uses it to dynamically call arbitrary PHP functions with arbitrary parameters, without any capability checks or input validation. An authenticated attacker with Subscriber-level access or higher can exploit this to execute arbitrary code on the server.

MitigationUpdate the UiPress lite plugin to the latest version (beyond 3.5.07) as soon as possible, and review user role permissions to limit access to trusted personnel only until the patch is 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify if UiPress lite plugin is installed
    Check the WordPress plugins directory or view the installed plugins list in wp-admin. Look for a folder named 'uipress-lite' or 'uipress' in wp-content/plugins/
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed UiPress lite version
    Check the plugin main file (usually uipress-lite.php) for the 'Version' header, or query the WordPress plugins API endpoint at /wp-json/wp/v2/plugins?search=uipress
    Affected if The version number is 3.5.07 or lower (any version up to and including 3.5.07)
  3. Verify the uip_process_form_input function is exposed
    Inspect the plugin source code for the uip_process_form_input function and its associated AJAX action hooks (look for 'wp_ajax_uip_process_form_input' or 'wp_ajax_nopriv_uip_process_form_input' in the code)
    Affected if The function exists and is registered as an AJAX handler accessible to authenticated users
  4. Confirm if subscriber-level or higher user accounts can exist
    In WordPress admin, go to Settings > General and check if 'Membership' is enabled (Anyone can register) and review which roles are available. Alternatively, query the wp_users table to check for accounts with subscriber role
    Affected if User registration is enabled OR subscriber-level accounts already exist in the system

A user is affected if UiPress lite version 3.5.07 or lower is installed AND the site allows authenticated users with Subscriber-level access or higher to exist.

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 the UiPress lite plugin to the latest version (beyond 3.5.07) as soon as possible, and review user role permissions to limit access to trusted personnel only until the patch is applied.

Recommended fix Moderate confidence

UiPress lite version 3.5.08 or higher

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate UiPress lite in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest fixed version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/uipress-lite/ and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the updated version number in the plugins list after updating

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-3053 — 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-3053 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