CVE-2024-33724
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 1.52.00 is vulnerable to Cross Site Scripting (XSS) via the groupe_id parameter to process/groupe_save.php.
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 confidenceSOPlanning 1.52.00 contains a stored Cross Site Scripting (XSS) vulnerability in process/groupe_save.php via the groupe_id parameter. The application fails to properly sanitize or validate user-supplied input before storing it, allowing an attacker to inject malicious JavaScript code that executes in the browsers of other users who view the affected data.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm SOPlanning installation and versionLocate the SOPlanning installation directory and check version.php or similar version file for the installed version numberAffected if The installed version is 1.52.00 or falls within an unpatched version range containing this vulnerability
-
Verify vulnerable file existsCheck if the file process/groupe_save.php exists in the web root or application directoryAffected if The file process/groupe_save.php is present in the installation
-
Confirm group management feature is enabledCheck if the groups functionality is accessible by logging in as a user and attempting to access group creation or management features, or inspect configuration files for group-related settingsAffected if The group management feature is enabled and accessible to users
-
Identify if groupe_id parameter accepts user inputReview application behavior or HTTP requests when saving group data - attempt to submit a test group with a non-standard groupe_id value and verify it is storedAffected if User-supplied input for groupe_id is accepted and stored without sanitization
-
Check if stored group data is displayed to usersIdentify pages or interfaces where group identifiers are rendered to users (such as group lists, task views, or user profiles) and verify if the data is displayed without output encodingAffected if Group identifiers are displayed in user-facing interfaces without proper output encoding
You are affected if SOPlanning version 1.52.00 is installed, the vulnerable file exists, and the group management feature is enabled, allowing stored XSS via the groupe_id parameter to be rendered to other users.
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.
From vendor dataImplement proper input validation and context-aware output encoding for the groupe_id parameter in groupe_save.php. Additionally, apply output escaping when the group identifier is rendered in any user-facing interface.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33724 — 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-2024-33724 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