dbcve.org
SoplanningApplication

CVE-2024-9574

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-07
Fix available
A fix is available. Upgrade to 1.45 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
SQL injection vulnerability in SOPlanning <1.45, via /soplanning/www/user_groupes.php in the by parameter, which could allow a remote user to submit a specially crafted query, allowing an attacker to retrieve all the information stored in the DB.

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 confidence

SQL injection vulnerability in SOPlanning versions before 1.45, located in /soplanning/www/user_groupes.php via the 'by' parameter, allowing remote attackers to inject malicious SQL queries and potentially retrieve all database contents.

MitigationUpgrade to SOPlanning version 1.45 or later which contains the fix for this SQL injection vulnerability; alternatively, implement proper input sanitization/parameterized queries in the affected file.

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
SoplanningApplication
Affected:< 1.45

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SOPlanning version
    Locate the version file or About page in your SOPlanning installation. Common locations include a version.php file, config file, or the /soplanning/about.php endpoint. Compare the version number against the vulnerable range (all versions before 1.45).
    Affected if The installed version is lower than 1.45 (e.g., 1.44, 1.43, etc.)
  2. Verify vulnerable file exists
    Check if the file /soplanning/www/user_groupes.php exists in your web server's document root or SOPlanning installation directory.
    Affected if The file exists and is accessible via the web server
  3. Confirm web application is exposed
    Determine if the SOPlanning web interface is accessible over HTTP/HTTPS to unauthenticated or authenticated users via the network.
    Affected if The application is network-accessible and the vulnerable endpoint can be reached
  4. Test for SQL injection via 'by' parameter
    If the above conditions are met, review access logs or use a safe parameter fuzzing tool to test the 'by' parameter in /soplanning/www/user_groupes.php for SQL injection behavior (unexpected database errors, unusual response times, or data exfiltration).
    Affected if The 'by' parameter accepts unsanitized input and exhibits SQL injection behavior

You are affected if SOPlanning version is below 1.45 AND the /soplanning/www/user_groupes.php file is present and accessible via the web interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.45 or later
Fixed in 1.45
Interim mitigation

Upgrade to SOPlanning version 1.45 or later which contains the fix for this SQL injection vulnerability; alternatively, implement proper input sanitization/parameterized queries in the affected file.

Recommended fix Moderate confidence

Soplanning >= 1.45

  1. 1. Backup your current Soplanning installation and database before proceeding with the upgrade.
  2. 2. Download Soplanning version 1.45 or later from the official vendor website.
  3. 3. Extract the new version files to your web server, preserving any custom configuration files if required.
  4. 4. Run the database upgrade scripts provided with the new version if applicable.
  5. 5. Verify the installation by accessing the application and testing the /soplanning/www/user_groupes.php functionality.
  6. 6. Confirm the 'by' parameter is properly sanitized and no longer vulnerable to SQL injection.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Soplanning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9574 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9574 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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