CVE-2025-62293
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 · uneditedSOPlanning is vulnerable to Broken Access Control in /status endpoint. Due to lack of permission checks in Project Status functionality an authenticated attacker is able to add, edit and delete any status. 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 confidenceSOPlanning versions prior to 1.55 contain a Broken Access Control vulnerability in the /status endpoint. The Project Status functionality lacks proper permission checks, allowing any authenticated user to add, edit, and delete any project status regardless of their authorization level.
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< 1.55.00CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SOPlanning versionCheck the application version displayed in the SOPlanning interface (typically in the footer, about page, or admin panel) or examine version files in the installation directoryAffected if The installed version is prior to 1.55.00 (e.g., 1.54.x, 1.53.x, etc.)
-
Locate the /status endpointAccess the application's web interface and navigate to the Project Status functionality, typically found under an admin or configuration section, or directly attempt to access the /status route via the URLAffected if The /status endpoint exists and is accessible within the application
-
Verify status management permissionsLog in with a low-privilege user account (non-admin) and attempt to add, edit, or delete a project status through the /status endpoint. Alternatively, inspect the access control logic in the source code for the status controllerAffected if A user with limited or no administrative privileges can successfully create, modify, or delete project statuses that they should not have access to modify
You are affected if SOPlanning version is below 1.55.00 and the /status endpoint allows unauthorized modification of project statuses by any authenticated user.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.55.00
Upgrade SOPlanning to version 1.55 or later, which contains the fix for this access control vulnerability.
1.55.00
- 1. Back up your current Soplanning installation and database
- 2. Download version 1.55.00 or later from the official Soplanning website (www.soplanning.org)
- 3. Upgrade your Soplanning installation to version 1.55.00 following the standard upgrade procedure
- 4. Verify the /status endpoint now properly enforces authorization checks
- 5. Test that authenticated users can only modify statuses they have permission to access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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