dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12963

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 LazyTasks – Project & Task Management with Collaboration, Kanban and Gantt Chart plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.2.29. This is due to the plugin not properly validating a user's identity via the 'wp-json/lazytasks/api/v1/user/role/edit/' REST API endpoint prior to updating their details like email address. This makes it possible for unauthenticated attackers to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account. It is also possible for attackers to abuse this endpoint to grant users with access to additional roles within the plugin

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 LazyTasks WordPress plugin has a privilege escalation vulnerability in its REST API endpoint (wp-json/lazytasks/api/v1/user/role/edit/) that fails to validate user identity before allowing email address changes and role modifications. Unauthenticated attackers can change any user's email (including administrators), then use WordPress password reset to take over the account, or directly assign elevated plugin roles to compromise the site.

MitigationUpdate the LazyTasks plugin to version 1.2.30 or later immediately. If no update is available, remove the plugin entirely. After patching, audit all administrator accounts for unauthorized changes and rotate passwords as a precaution.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify LazyTasks plugin is installed
    Check the WordPress plugins directory or wp-admin plugins list for the LazyTasks plugin
    Affected if LazyTasks plugin is not found in the installation
  2. Determine installed LazyTasks version
    Read the plugin header in wp-content/plugins/lazytasks/lazytasks.php or check the plugins admin page for the version number
    Affected if Version is unknown or below 1.2.30 (vulnerable)
  3. Confirm plugin is active
    Check if LazyTasks is activated in WordPress admin under Plugins > Installed Plugins
    Affected if Plugin is active and vulnerable version is installed
  4. Test vulnerable REST API endpoint accessibility
    Send a GET request to wp-json/lazytasks/api/v1/user/role/edit/ using curl or browser developer tools
    Affected if Endpoint returns HTTP 200 or any JSON response (indicating the vulnerable endpoint exists and is reachable)
  5. Check REST API authorization behavior
    Send a POST request to the endpoint with modified user data (e.g., different email) without providing authentication credentials
    Affected if Request succeeds without returning 401/403 authentication errors (unauthenticated modification is possible)

A user is affected if LazyTasks plugin version is below 1.2.30 (or cannot be determined) AND the vulnerable REST API endpoint is accessible and allows unauthenticated modifications.

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 LazyTasks plugin to version 1.2.30 or later immediately. If no update is available, remove the plugin entirely. After patching, audit all administrator accounts for unauthorized changes and rotate passwords as a precaution.

Recommended fix Moderate confidence

LazyTasks plugin version 1.2.30 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the LazyTasks plugin
  4. Check if an update is available for the LazyTasks plugin
  5. If an update is available, click 'Update Now' to update the plugin to the latest version
  6. After updating, verify the plugin is running version 1.2.30 or higher
  7. Alternatively, download the latest version of the LazyTasks plugin from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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