dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-1309

HIGH · 8.8 CVSS v3.1 Published 2025-03-07
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 unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the uip_save_form_as_option() function in all versions up to, and including, 3.5.04. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 lacks a capability check on the uip_save_form_as_option() function, allowing any authenticated user with Subscriber-level access or higher to call this function and modify arbitrary WordPress options. Attackers can change the default user registration role to Administrator and enable user registration, then register an admin account to fully compromise the site.

MitigationUpdate the plugin to version 3.5.05 or later which includes proper capability validation. If immediate update is not possible, implement WAF rules to block unauthorized access to the affected endpoint and temporarily disable user registration.

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. Confirm UiPress lite plugin is installed
    Check the WordPress plugins directory or access wp-admin > Plugins to see if UiPress lite is active
    Affected if UiPress lite plugin is installed and active on the site
  2. Check installed plugin version
    Navigate to Plugins > Installed Plugins in wp-admin and find the UiPress lite entry to view its version number
    Affected if Version is lower than 3.5.05 (the fixed version)
  3. Verify user registration settings
    Go to Settings > General in wp-admin and check if Anyone can register is enabled and New User Default Role is set to Administrator
    Affected if User registration is enabled with Administrator as the default role
  4. Audit user accounts for unauthorized administrators
    Go to Users > All Users in wp-admin and review the list for administrator accounts you did not create, or query the wp_users and wp_usermeta tables directly
    Affected if Unexpected administrator accounts exist in the system
  5. Check wp_options for recent unauthorized modifications
    Query the wp_options table for recent changes to users_can_register, default_role, or other critical settings using: SELECT option_name, option_value, autoload FROM wp_options WHERE option_name IN ('users_can_register','default_role','admin_email') ORDER BY option_id DESC LIMIT 20
    Affected if These options were changed unexpectedly or without administrator action

A site is affected if UiPress lite version is below 3.5.05 AND user registration is enabled with Administrator as the default role, or if unauthorized administrator accounts 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 plugin to version 3.5.05 or later which includes proper capability validation. If immediate update is not possible, implement WAF rules to block unauthorized access to the affected endpoint and temporarily disable user registration.

Recommended fix Moderate confidence

UiPress lite version 3.5.05 or later

  1. Update the UiPress lite plugin to version 3.5.05 or later through WordPress admin > Plugins > Update Now
  2. Alternatively, navigate to Dashboard > Updates and apply the available update
  3. After updating, verify the fix by confirming the uip_save_form_as_option() function now includes a capability check
  4. Review user roles and options (especially default_role and users_can_register) to ensure no unauthorized changes were made
Caveat None documented for this update - this is a security patch with no breaking changes expected

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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