CVE-2024-29876
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 · uneditedSQL injection vulnerability in Sentrifugo 3.2, through /sentrifugo/index.php/reports/activitylogreport, 'sortby' 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 confidenceSQL injection vulnerability in Sentrifugo 3.2 allows remote attackers to inject malicious SQL queries through the 'sortby' parameter at /sentrifugo/index.php/reports/activitylogreport, enabling extraction of sensitive data from the database.
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= 3.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Sentrifugo installationCheck if the application is present by accessing the application's web root directory or by attempting to reach known Sentrifugo paths (e.g., /sentrifugo/, /index.php) on the serverAffected if The application is not Sentrifugo or is a different product entirely, this CVE does not apply
-
Identify installed Sentrifugo versionLocate version information in the application (typically found in version files, about pages, or the application metadata within the web root) and compare to 3.2Affected if The installed version is exactly 3.2, proceed to next check. If different version, this specific CVE does not apply
-
Verify vulnerable endpoint existsAttempt to access the path /sentrifugo/index.php/reports/activitylogreport (or the equivalent path in your installation) via HTTP request to confirm the endpoint is routableAffected if The endpoint returns a 200 OK or application response, confirming the reports module is accessible. A 404 indicates the endpoint does not exist and this specific CVE cannot be exploited
-
Test 'sortby' parameter acceptanceSend a request to the activitylogreport endpoint including any value for the 'sortby' parameter (e.g., ?sortby=test) and observe if the application processes it without errorAffected if The application accepts and processes the sortby parameter without rejecting it, the vulnerability is potentially present and the environment is affected
Environment is affected only if running Sentrifugo version 3.2 with the /reports/activitylogreport endpoint accessible and the 'sortby' parameter functional.
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 dataImplement parameterized queries or prepared statements for all database operations using the 'sortby' parameter, and apply input validation to sanitize user-supplied values before executing SQL queries.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29876 — 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-29876 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