CVE-2024-33722
SQL Injection in SOPlanning 1.52.00 via projets.php
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fuzzlove | soplanning | 1.52.00 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2024-33722 is an authenticated SQL injection vulnerability in SOPlanning version 1.52.00. It occurs in the 'projets.php' page where parameters such as 'filtreGroupeProjet', 'statut[]', and 'rechercheProjet' can be manipulated to inject malicious SQL queries.
An attacker must first authenticate, which can be done using a CSRF exploit, and then send crafted GET or POST requests to execute arbitrary SQL commands.
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized data access, data manipulation, or even complete database takeover.
This means an attacker could view sensitive information, alter data, or disrupt the normal operation of the application.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted authenticated requests to the 'projets.php' page, specifically manipulating parameters such as 'statut[]', 'filtreGroupeProjet', or 'rechercheProjet' to test for SQL injection.
A sample detection method involves using a curl command to inject a time-based SQL payload that causes a delay if the injection is successful.
- Authenticate to the SOPlanning application.
- Send a crafted curl request similar to the following example to test for SQL injection:
- curl -i -s -k --cookie "SESSION=your_session_cookie" "http://target/projets.php?statut[]=1' AND IF(SLEEP(10),1,0)-- -"
If the response time is significantly delayed (e.g., about 10 seconds), it indicates the presence of the SQL injection vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
CVE-2024-33722 is an authenticated SQL injection vulnerability that allows an attacker to execute arbitrary SQL commands, potentially leading to unauthorized access or manipulation of sensitive data stored in the SOPlanning database.
Such unauthorized access or data manipulation can compromise the confidentiality, integrity, and availability of personal or sensitive information, which may result in non-compliance with data protection regulations and standards like GDPR or HIPAA.
Specifically, if personal data protected under GDPR or health information protected under HIPAA is exposed or altered due to this vulnerability, the affected organization could face legal penalties, mandatory breach notifications, and reputational damage.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL injection vulnerability in SOPlanning 1.52.00, immediate steps include restricting access to the 'projets.php' page to only trusted authenticated users and monitoring for unusual activity involving the 'statut[]' parameter.
Additionally, applying input validation and sanitization on parameters such as 'filtreGroupeProjet', 'statut[]', and 'rechercheProjet' can help prevent malicious SQL injection attempts.
If possible, update or patch SOPlanning to a version where this vulnerability is fixed, or implement web application firewall (WAF) rules to detect and block SQL injection patterns targeting these parameters.
Since exploitation requires authentication, ensure strong authentication mechanisms and consider implementing CSRF protections to prevent attackers from leveraging authenticated sessions.