CVE-2025-62295
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 Stored XSS in /groupe_form endpoint. Malicious attacker with medium privileges can inject arbitrary HTML and JS into website, which will be rendered/executed when opening editor. 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 stored Cross-Site Scripting (XSS) vulnerability in the /groupe_form endpoint. An authenticated user with medium-level privileges can inject arbitrary HTML and JavaScript code into form fields, which is then persistently stored on the server and executed whenever other users access the editor functionality.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 SOPlanning installationLocate the SOPlanning web application directory or check running web services for SOPlanning (commonly found in /var/www/soplanning, /opt/soplanning, or similar web root directories)Affected if SOPlanning software is present in the environment
-
Determine installed SOPlanning versionCheck the version file or header typically found in the SOPlanning installation - often accessible via the application's login page source, version.php file, or by accessing /version endpoint if availableAffected if The installed version is earlier than 1.55.00 (e.g., 1.54.x, 1.53.x, etc.)
-
Verify /groupe_form endpoint existsAttempt to access the /groupe_form endpoint via HTTP request (e.g., GET https://your-server/soplanning/groupe_form) - this is the vulnerable form endpoint for group managementAffected if The endpoint responds and displays a form interface, indicating the vulnerable functionality is present
-
Confirm authentication requirementVerify that access to /groupe_form requires authenticated session with medium-level user privileges (standard user rights, not admin)Affected if A user with standard/medium privileges can access and submit the form, which would allow XSS injection into stored fields
If SOPlanning versions prior to 1.55.00 are installed AND the /groupe_form endpoint is accessible to authenticated medium-privilege users, the environment is affected by this stored XSS vulnerability.
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. Additionally, implement proper input validation and output encoding on the /groupe_form endpoint to prevent XSS attacks.
1.55.00
- Upgrade Soplanning to version 1.55.00 or later from https://www.soplanning.org
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62295 — 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-62295 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