dbcve.org
SoplanningApplication

CVE-2025-62730

HIGH · 8.8 CVSS v3.1 Published 2025-11-20
Fix available
A fix is available. Upgrade to 1.55.00 or later.
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
SOPlanning is vulnerable to Privilege Escalation in user management tab. Users with user_manage_team role are allowed to modify permissions of users. However, they are able to assign administrative permissions to any user including themselves. This allow a malicious authenticated attacker with this role to escalate to admin privileges. This issue affects both Bulk Update functionality and regular edition of user's right and privileges. This issue was fixed in version 1.55.

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

SOPlanning contains a privilege escalation vulnerability in its user management functionality. Users assigned the 'user_manage_team' role can modify other users' permissions but are incorrectly allowed to grant themselves or others administrative privileges. This affects both bulk update and individual user editing interfaces, allowing authenticated users with this role to obtain full admin access.

MitigationUpgrade to SOPlanning version 1.55 or later to apply the fix. Additionally, audit accounts with the user_manage_team role to confirm no unauthorized admin accounts were created, and consider limiting this role to only highly trusted personnel until the upgrade is completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SoplanningApplication
Affected:< 1.55.00

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 installed SOPlanning version
    Locate the version file or check the application footer/admin panel for the current Soplanning version number
    Affected if The installed version is lower than 1.55.00 (e.g., 1.54.x, 1.53.x, etc.)
  2. Enumerate users with user_manage_team role
    Access the user management section and filter or search for users assigned the 'user_manage_team' role; query the users table if database access is available
    Affected if Any user account is assigned the user_manage_team role
  3. Audit administrator-level accounts
    Review all users with administrative privileges; check user profiles and permissions tables for accounts with admin or superuser status that are unexpected
    Affected if There are admin accounts that were created or modified by users with only the user_manage_team role, or admin accounts that should not exist
  4. Inspect bulk user update interface
    Locate the bulk user update/edit functionality in the admin panel and verify what permission changes can be performed by non-administrators
    Affected if The bulk update interface allows users with user_manage_team role to modify permission levels to administrator
  5. Inspect individual user editing interface
    Locate the individual user edit functionality and verify what permission modifications are available to users with user_manage_team role
    Affected if The individual user edit interface permits granting administrator privileges without elevated admin authentication

Your environment is affected if SOPlanning version is below 1.55.00 AND any user accounts possess the user_manage_team role, regardless of whether unauthorized admin accounts are currently visible.

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
Upgrade available Upgrade to 1.55.00 or later
Fixed in 1.55.00
Interim mitigation

Upgrade to SOPlanning version 1.55 or later to apply the fix. Additionally, audit accounts with the user_manage_team role to confirm no unauthorized admin accounts were created, and consider limiting this role to only highly trusted personnel until the upgrade is completed.

Recommended fix High confidence

1.55.00

  1. 1. Back up the current Soplanning installation and database before upgrading.
  2. 2. Navigate to the official Soplanning download page at www.soplanning.org.
  3. 3. Download version 1.55.00 (the fixed release).
  4. 4. Install or update the Soplanning application to version 1.55.00 following the standard upgrade procedure.
  5. 5. Verify that the upgrade was successful by logging in and confirming the version number.
  6. 6. Test that users with the user_manage_team role can no longer assign administrative permissions to themselves or other users.

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

Fix this in Soplanning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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