LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7719: Prototype Pollution

Versions of package locutus before 2.0.12 are vulnerable to prototype Pollution via the php.strings.parse_str function.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-7719 affects the JavaScript package locutus before 2.0.12. A flaw in php.strings.parse_str can allow prototype pollution, potentially letting untrusted input change shared object behavior inside an application. The business risk is highest where locutus parses attacker-controlled strings in internet-facing services.

Executive priority

Treat as high-priority remediation for services using locutus in request-processing paths. The worst-case impact is severe, but urgency depends on confirmed vulnerable usage and whether untrusted input reaches the affected function.

Technical view

The vulnerability is prototype pollution in locutus php.strings.parse_str before version 2.0.12. CVSS 3.1 is 9.8, with network attack vector, low complexity, no privileges, and no user interaction. The source bundle links remediation context to the locutus pull request and Snyk advisory.

Likely exposure

Exposure is likely limited to JavaScript applications that depend on vulnerable locutus versions and use php.strings.parse_str with untrusted or externally influenced input.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates remote, unauthenticated potential impact, and the CVSS exploit maturity field indicates proof-of-concept status.

Researcher notes

The provided affected-version metadata is sparse, but the description states locutus versions before 2.0.12 are vulnerable. Focus validation on actual dependency resolution and parse_str data flow. Do not assume exposure from package presence alone.

Mitigation direction

  • Upgrade locutus to 2.0.12 or later.
  • Check Snyk and locutus project guidance for current remediation details.
  • Review lockfiles for transitive locutus dependency paths.
  • Restrict untrusted input reaching php.strings.parse_str where upgrade is delayed.
  • Add regression tests for prototype pollution resistance.

Validation and detection

  • Identify all package manifests and lockfiles referencing locutus.
  • Confirm deployed artifacts run locutus 2.0.12 or later.
  • Search code for php.strings.parse_str usage.
  • Review whether parse_str receives user-controlled strings.
  • Run dependency scanning against production lockfiles.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-7719 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-7719Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/alocutus0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.