dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-8504

HIGH · 8.8 CVSS v3.1 Published 2024-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
High EPSS 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
An attacker with authenticated access to VICIdial as an "agent" can execute arbitrary shell commands as the "root" user. This attack can be chained with CVE-2024-8503 to execute arbitrary shell commands starting from an unauthenticated perspective.

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 · moderate confidence

Authenticated VICIdial agents can execute arbitrary shell commands with root privileges due to insufficient input validation and privilege separation in agent-accessible functions. This allows complete system compromise from a standard agent account.

MitigationRestrict agent-level access to command execution functions, implement proper input sanitization, apply principle of least privilege, and apply vendor patches when available. Also address CVE-2024-8503 to prevent the full attack chain from unauthenticated starting point.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 VICIdial installation and version
    Locate the VICIdial installation directory (commonly /var/www/html/vicidial or /srv/www/htdocs/vicidial) and check the version.php or version.txt file within the installation. Also run 'grep -i version /path/to/vicidial/*.*' to find version information.
    Affected if VICIdial is installed and the installed version is unknown, unpatched, or earlier than the patched release that addresses CVE-2024-8504.
  2. Verify existence of agent accounts
    Check the vicidial_users table in the MySQL/PostgreSQL database for records where user_level is less than 5 (agent-level accounts). Run: mysql -e 'SELECT user,user_level,active FROM vicidial_users;' <database_name>
    Affected if Active agent-level accounts (user_level 1-4) exist in the system.
  3. Inspect agent-accessible script directories for modifications
    Review PHP files in the agent interface directories (such as /agent, /agc, or similar) for unexpected functions that execute shell commands. Compare file checksums or timestamps against known-good baselines: find /path/to/vicidial -name '*.php' -mtime -30
    Affected if PHP scripts in agent-accessible directories contain shell execution functions (exec, system, passthru, shell_exec, backticks) that accept user input without sanitization, or show recent unauthorized modifications.
  4. Review web server and audit logs for suspicious command execution
    Examine web access logs (typically in /var/log/httpd or /var/log/nginx) for requests from agent IP addresses or sessions that include unusual parameters. Search for patterns like '|', ';', '`', or '$(' in GET/POST parameters. Also check /var/log/audit/audit.log for commands run by the apache/nginx user.
    Affected if Logs show shell command patterns or suspicious parameter injection attempts originating from agent-accessible endpoints, or commands executed by the web server user that match known exploitation patterns.
  5. Check for root-level processes spawned from web server context
    Run 'ps aux | grep -E "(root|apache|nginx|www-data)" | head -20' and review process trees. Look for root-owned processes with suspicious command lines, or processes running under the web server user that have unexpected parent-child relationships.
    Affected if Root-owned processes show execution traces linked to agent session parameters, or the web server user has recently spawned processes it normally should not.

The environment is likely affected if VICIdial is installed with active agent accounts, the installation lacks the CVE-2024-8504 patch, or forensic evidence shows command injection from agent-accessible endpoints.

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

Restrict agent-level access to command execution functions, implement proper input sanitization, apply principle of least privilege, and apply vendor patches when available. Also address CVE-2024-8503 to prevent the full attack chain from unauthenticated starting point.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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