CVE-2024-33722
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 SQL Injection by an authenticated user via projets.php with statut[].
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 SQL Injection vulnerability in the projets.php file via the statut[] parameter. An authenticated attacker can inject malicious SQL queries through this array parameter, potentially allowing data exfiltration or manipulation of the database.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 versionLocate the version file or header in the SOPlanning installation directory. Common locations include a version.php file, README file, or the admin interface version display. Check the application footer or About page in the web interface.Affected if The installed version is 1.52.00, or the version cannot be determined but the application is SOPlanning and matches the vulnerable release.
-
Verify projets.php exists and is accessibleCheck if the file projets.php exists in the web application's root or appropriate module directory. Confirm it is accessible via HTTP/HTTPS requests to the web server.Affected if The projets.php file is present and reachable via the web interface.
-
Confirm authentication is enabledVerify that the SOPlanning application requires user authentication to access projets.php. Check the application's session management and login requirements.Affected if Authentication is enabled and a valid user account exists, which would allow an attacker to reach the vulnerable parameter.
-
Examine statut[] parameter handling in projets.phpIf you have access to the source code, inspect the projets.php file for handling of the statut[] array parameter. Look for direct use of this parameter in SQL queries without proper sanitization or use of prepared statements.Affected if The code shows that the statut[] parameter is directly interpolated into SQL queries without parameterized binding.
The environment is affected if SOPlanning version 1.52.0 is installed, the projets.php file is accessible, and the statut[] parameter is processed in SQL queries without parameterized statements.
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 dataReplace dynamic SQL queries in projets.php with parameterized queries or prepared statements, and implement strict input validation on the statut[] parameter to prevent SQL injection attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33722 — 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-33722 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