dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-48082

HIGH · 8.8 CVSS v3.1 Published 2025-10-22
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
Incorrect Privilege Assignment vulnerability in Progress Planner Progress Planner progress-planner allows Privilege Escalation.This issue affects Progress Planner: from n/a through <= 1.8.0.

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 · moderate confidence

WordPress plugin vulnerability where incorrect privilege assignment allows lower-privileged users (such as subscribers or contributors) to perform administrative actions they should not have access to, enabling privilege escalation to higher permission levels.

MitigationUpdate Progress Planner plugin to version 1.8.1 or later; verify that proper capability checks are enforced for all user role actions.

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 Progress Planner plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Progress Planner' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed plugin version
    In the plugins list, click on 'View Details' for Progress Planner or check the plugin header in /wp-content/plugins/progress-planner/ folder for the version number.
    Affected if The installed version is lower than 1.8.1.
  3. Review user role capabilities
    Navigate to Users > All Users in WordPress admin. Check if subscriber or contributor roles exist and examine what capabilities they possess by using a role editor plugin or database query on wp_usermeta.
    Affected if Subscriber or contributor roles have administrative or elevated capabilities they should not possess.
  4. Inspect plugin role/settings configuration
    Check the plugin settings page at Settings > Progress Planner (or similar) to see which user roles are permitted to access or configure the plugin.
    Affected if The plugin allows subscriber or contributor roles to access or modify settings that should require administrator privileges.

A user is affected if the Progress Planner plugin is installed with a version lower than 1.8.1 and subscriber or contributor roles have been granted elevated administrative capabilities or access to plugin settings.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Progress Planner plugin to version 1.8.1 or later; verify that proper capability checks are enforced for all user role actions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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