dbcve.org
Locutus PhpApplication · Locutus

CVE-2020-13619

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-01
Fix available
A fix is available. Upgrade to after 2.0.11 or later.
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
php/exec/escapeshellarg in Locutus PHP through 2.0.11 allows an attacker to achieve code execution.

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

The escapeshellarg function in Locutus PHP through version 2.0.11 contains a vulnerability that allows an attacker to bypass proper shell argument escaping and achieve arbitrary code execution. This command injection flaw in the php/exec/escapeshellarg component can be exploited by supplying specially crafted input.

MitigationUpgrade Locutus PHP to version 2.0.12 or later where the escapeshellarg vulnerability has been patched. If immediate patching is not possible, avoid passing untrusted input through the escapeshellarg function and implement additional input validation.

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
Locutus PhpApplication
Affected:<= 2.0.11

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 Locutus PHP installation
    Locate the Locutus PHP library in your codebase or dependencies (commonly in vendor/, node_modules/, or as a direct include). Check package.json, composer.json, or the library's main index file for version information.
    Affected if Locutus PHP version 2.0.11 or earlier is installed
  2. Locate the escapeshellarg component
    Search for files containing 'escapeshellarg' in the php/exec/ directory of the Locutus library, or check if the exec/escapeshellarg component is imported/required in your application.
    Affected if The php/exec/escapeshellarg component from Locutus is present and being used
  3. Identify usage of escapeshellarg with external input
    Search your codebase for calls to the Locutus escapeshellarg function. Trace the data flow to determine whether user-supplied, API-derived, or otherwise untrusted input is being passed as the argument.
    Affected if Untrusted or user-controlled input is passed through the Locutus escapeshellarg function
  4. Compare installed version against affected range
    If version information is available, compare it to the affected range: any version of Locutus PHP <= 2.0.11 is vulnerable.
    Affected if Installed Locutus PHP version is 2.0.11 or earlier

You are affected if your environment uses Locutus PHP version 2.0.11 or earlier and passes untrusted input through the php/exec/escapeshellarg component.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.11
Interim mitigation

Upgrade Locutus PHP to version 2.0.12 or later where the escapeshellarg vulnerability has been patched. If immediate patching is not possible, avoid passing untrusted input through the escapeshellarg function and implement additional input validation.

Recommended fix Moderate confidence

Locutus PHP version 2.0.12 or later

  1. 1. Check current Locutus version in your project: npm list locutus or yarn list locutus
  2. 2. Identify all JavaScript/Node.js files that import or use the 'php/exec/escapeshellarg' function from Locutus
  3. 3. Update Locutus to version 2.0.12 or later: npm update [email protected] or yarn upgrade [email protected]
  4. 4. Verify the upgrade was successful: npm list locutus
  5. 5. Test your application to ensure the php/exec/escapeshellarg function still works correctly with the updated library
  6. 6. Rebuild and redeploy any services that depend on this package
Caveat Minimal risk - this is a patch release fixing a security vulnerability in a utility function; however, test thoroughly to verify escaped shell arguments behave as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Locutus Php Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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