Authenticated status tampering via missing permission checks
Published Nov 20, 2025 · Updated Nov 20, 2025
Missing authorization in SOPlanning before 1.55 allows remote authenticated users to add, edit, or delete any project status. The /status endpoint's Project Status handlers perform state-changing operations without checking whether the requesting account has permission to manage statuses. The gate is possession of any valid account, and the bounded consequence is unauthorized modification or deletion of project-status records.
Summary
What happened
Missing authorization in SOPlanning before 1.55 allows remote authenticated users to add, edit, or delete any project status. The /status endpoint's Project Status handlers perform state-changing operations without checking whether the requesting account has permission to manage statuses. The gate is possession of any valid account, and the bounded consequence is unauthorized modification or deletion of project-status records.
The record
- CVE
- CVE-2025-62293
- Published
- Nov 20, 2025
- Updated
- Nov 20, 2025
- Vendor
- SOPlanning
- Product
- SOPlanning
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 20, 2025CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.55
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo