How severe is CVE-2019-15489?

CVE-2019-15489 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-15489?

CVE-2019-15489 affects the following packages: jsdecena/laracom (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-15489?

Update jsdecena/laracom to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15489 is resolved across your whole dependency graph.

How do I detect CVE-2019-15489 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jsdecena/laracom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-15489 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2019-15489 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-15489, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-15489?

CVE-2019-15489 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-15489?

CVE-2019-15489 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-15489 published, and has it been updated?

CVE-2019-15489 was published on August 26, 2019 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2019-15489 — laracom

MEDIUMFix: Laracommerce/laracom#211

CVE-2019-15489 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in jsdecena/laracom. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for jsdecena/laracom — see the affected versions and patch details below.

laracom Cross-site Scripting

Also known asGHSA-qc2p-6qrf-25j2

Published

Aug 26, 2019

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘jsdecena/laracom

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

laracom (aka Laravel FREE E-Commerce Software) 1.4.11 has a Cross-site Scripting vulnerability via search query.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`jsdecena/laracom`	≥ 1.4.11&&< 1.5.0	1.5.0`composer require jsdecena/laracom:^1.5.0`

Affected Products

1 product · 1 configurations

Application

laracomlaracom

1 version

1.4.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

laracom (aka Laravel FREE E-Commerce Software) 1.4.11 has search?q= XSS.

github.comNVDAug 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jsdecena/laracom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jsdecena/laracom to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15489 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

laracom (aka Laravel FREE E-Commerce Software) 1.4.11 has a Cross-site Scripting vulnerability via search query.

O3 Security · Impact-Aware SCA

Is CVE-2019-15489 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Aug 26, 2019

First exploit

Aug 26, 2019

Same day as disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2019-15489

GHSA-qc2p-6qrf-25j2

References

Advisorynvd.nist.gov · CVE 2019 15489 Fixgithub.com Webgithub.com · 36ff6a5c4a7878c719304e9d9a5f1fc74a5af474 Packagegithub.com · laracom

Related vulnerabilities

Also affects jsdecena/laracom

This CVE is medium severity, in line with the other 1 CVE affecting jsdecena/laracom.

CVE-2022-0472

Same weakness: CWE-79

This CVE is medium severity; 7 of 7 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246CVE-2026-118251CVE-2026-118253Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2019-15489 — laracom

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-15489 in your dependencies?