dbcve.org
SentrifugoApplication · Sapplica

CVE-2024-29870

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Sentrifugo 3.2, through /sentrifugo/index.php/index/getdepartments/format/html, 'business_id' parameter./sentrifugo/index.php/index/getdepartments/format/html, 'business_id' parameter. The exploitation of this vulnerability could allow a remote user to send a specially crafted query to the server and extract all the data from it.

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 Sentrifugo 3.2 allows remote attackers to inject malicious SQL queries via the 'business_id' parameter in the /sentrifugo/index.php/index/getdepartments/format/html endpoint. The lack of proper input sanitization or parameterized queries enables extraction of sensitive data from the database.

MitigationImplement prepared statements/parameterized queries for all database operations involving user input. Apply input validation and escaping for the 'business_id' parameter, and conduct a comprehensive code audit for additional SQL injection vulnerabilities.

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
SentrifugoApplication
Affected:= 3.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Sentrifugo installation and version
    Locate the Sentrifugo installation directory and check the version file, typically found in a version.php, about.php, or config file within the application root. Common paths include /sentrifugo/application/configs/ or check the main index.php for version references.
    Affected if The installed version is exactly 3.2 (version 3.2). Earlier versions or later patches are not affected by this specific CVE.
  2. Verify vulnerable endpoint exists
    Check if the file /sentrifugo/index.php exists and if the path /index/getdepartments/format/html is accessible within the application's routing structure. Inspect the application's URL routing configuration or attempt to access the endpoint if you have a test environment.
    Affected if The endpoint /index/getdepartments/format/html is present and routable in the application.
  3. Locate the getdepartments controller
    Navigate to the application source code and find the controller handling the getdepartments action, typically in /sentrifugo/application/modules/index/controllers/ or similar. Inspect the getdepartmentsAction or getdepartments method.
    Affected if The controller processes the 'business_id' parameter directly without using prepared statements or parameterized queries in its database queries.
  4. Inspect database query handling for business_id
    Review the getdepartments method code to identify how the 'business_id' parameter from the request is incorporated into SQL queries. Search for direct string concatenation or interpolation of this parameter into query strings.
    Affected if The 'business_id' parameter is directly concatenated into SQL queries without sanitization, escaping, or use of parameterized queries.

You are affected if Sentrifugo version 3.2 is installed and the getdepartments endpoint processes the business_id parameter via unsanitized string concatenation in SQL queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations involving user input. Apply input validation and escaping for the 'business_id' parameter, and conduct a comprehensive code audit for additional SQL injection vulnerabilities.

Fix this in Sentrifugo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29870 — 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-29870 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