dbcve.org
SentrifugoApplication · Sapplica

CVE-2024-29872

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/empscreening/add, 'agencyids' 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 execute arbitrary SQL queries through the 'agencyids' parameter at /sentrifugo/index.php/empscreening/add, enabling complete database extraction.

MitigationApply vendor patch or upgrade to fixed version; if unavailable, implement parameterized queries/prepared statements for the affected parameter and validate/sanitize all user inputs.

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. Confirm Sentrifugo installation exists
    Locate the Sentrifugo web application directory. Common paths include /var/www/html/sentrifugo, /www/sentrifugo, or check your web server document root for a 'sentrifugo' folder containing index.php
    Affected if The Sentrifugo application directory is found on the system
  2. Identify installed Sentrifugo version
    Check the version file in the Sentrifugo installation. Typically found in a version.php, CHANGELOG file, or application configuration. You can also check the composer.json or any VERSION file in the root directory
    Affected if The installed version is exactly 3.2 (matching = 3.2)
  3. Verify empscreening module is enabled
    Check if the empscreening module is present and enabled in the application configuration. Look for the module directory at /sentrifugo/application/modules/empscreening and verify it is not disabled in the application config
    Affected if The empscreening module exists and is active in the Sentrifugo installation
  4. Confirm vulnerable endpoint is accessible
    Verify the URL /sentrifugo/index.php/empscreening/add is accessible from the web server. Check web server access logs for requests to this endpoint. You can also verify the route exists by checking the module's controllers
    Affected if The /sentrifugo/index.php/empscreening/add endpoint responds to requests (module is accessible via web)
  5. Check for untrusted input handling on agencyids parameter
    Review the empscreening controller code for the add action. Examine how the 'agencyids' parameter is handled - look for direct use in SQL queries without parameterized queries or input validation
    Affected if The agencyids parameter is used in database queries without prepared statements or input sanitization

The environment is affected if Sentrifugo version 3.2 is installed, the empscreening module is enabled, and the /empscreening/add endpoint with the agencyids parameter is accessible without proper SQL query parameterization.

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

Apply vendor patch or upgrade to fixed version; if unavailable, implement parameterized queries/prepared statements for the affected parameter and validate/sanitize all user inputs.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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