dbcve.org
SentrifugoApplication · Sapplica

CVE-2024-29875

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/default/reports/exportactiveuserrpt, 'sort_name' 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 through the 'sort_name' parameter in the /sentrifugo/index.php/default/reports/exportactiveuserrpt endpoint. The vulnerability enables complete database compromise including unauthorized data extraction.

MitigationImplement parameterized queries (prepared statements) for the sort_name parameter in the affected report export functionality, or apply vendor-supplied patch if available. Consider temporarily disabling the endpoint until remediation is complete.

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 version
    Locate the Sentrifugo installation directory and check the version file or header. Common locations include a version.php file, README, or the application header/splash page. Compare the installed version to the affected version (3.2).
    Affected if The installed Sentrifugo version is exactly 3.2.
  2. Verify vulnerable endpoint exists
    Check if the application serves the path /sentrifugo/index.php/default/reports/exportactiveuserrpt. This can be done by reviewing web server configuration, route definitions, or attempting to access the endpoint (in a non-production environment only).
    Affected if The /sentrifugo/index.php/default/reports/exportactiveuserrpt endpoint exists and responds in the application.
  3. Confirm sort_name parameter acceptance
    Review the application code handling the exportactiveuserrpt endpoint. Locate the controller handling this route and verify it accepts and processes a 'sort_name' HTTP parameter without immediate validation or parameterization.
    Affected if The endpoint accepts a 'sort_name' parameter that gets used in database queries without visible sanitization or prepared statement usage in the code.
  4. Inspect database query implementation
    Examine the PHP code for the reports/exportactiveuserrpt functionality. Search for direct string concatenation or improper interpolation of the sort_name parameter into SQL queries. Look for prepare()/bindParam() usage.
    Affected if The sort_name parameter is concatenated directly into SQL strings rather than being passed as a bound parameter to a prepared statement.
  5. Check for application-level SQL injection protections
    Review any WAF configurations, input filtering middleware, or custom sanitization functions that may be in place before the sort_name parameter reaches the database layer.
    Affected if No input validation, WAF rules, or parameterized queries are present to mitigate SQL injection in this parameter.

You are affected if running Sentrifugo version 3.2 with the /sentrifugo/index.php/default/reports/exportactiveuserrpt endpoint accessible and the sort_name parameter processed without prepared statements.

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 parameterized queries (prepared statements) for the sort_name parameter in the affected report export functionality, or apply vendor-supplied patch if available. Consider temporarily disabling the endpoint until remediation is complete.

Fix this in Sentrifugo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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