How severe is CVE-2019-6341?

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

Which packages are affected by CVE-2019-6341?

CVE-2019-6341 affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-6341?

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

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

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

How do I mitigate CVE-2019-6341 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-6341 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-6341 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2019-6341 has an EPSS (Exploit Prediction Scoring System) score of 12.2%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2019-6341?

CVE-2019-6341 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-6341 published, and has it been updated?

CVE-2019-6341 was published on March 26, 2019 and was last updated on October 24, 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-6341 — core

MEDIUM

CVE-2019-6341 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in drupal/core. EPSS puts its 30-day exploitation probability at 12.2% (96th percentile). A fix is available for drupal/core — see the affected versions and patch details below.

Drupal Cross Site Scripting (XSS) vulnerability

Also known asDRUPAL-CORE-2019-004GHSA-cmmh-8mwp-gq5p

Published

Mar 26, 2019

Updated

Oct 24, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

12.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% 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

6 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/drupal🐘drupal/drupal🐘drupal/drupal

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

In Drupal 7 versions prior to 7.65; Drupal 8.6 versions prior to 8.6.13;Drupal 8.5 versions prior to 8.5.14. Under certain circumstances the File module/subsystem allows a malicious user to upload a file that can trigger a cross-site scripting (XSS) vulnerability.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 7.0.0&&< 7.65.0	7.65.0`composer require drupal/core:^7.65.0`
🐘Packagist	`drupal/core`	≥ 8.0.0&&< 8.5.14	8.5.14`composer require drupal/core:^8.5.14`
🐘Packagist	`drupal/core`	≥ 8.6.0&&< 8.6.13	8.6.13`composer require drupal/core:^8.6.13`
🐘Packagist	`drupal/drupal`	≥ 7.0.0&&< 7.65.0	7.65.0`composer require drupal/drupal:^7.65.0`
🐘Packagist	`drupal/drupal`	≥ 8.0.0&&< 8.5.14	8.5.14`composer require drupal/drupal:^8.5.14`
🐘Packagist	`drupal/drupal`	≥ 8.6.0&&< 8.6.13	8.6.13`composer require drupal/drupal:^8.6.13`

Affected Products

3 products · 6 configurations

debian linuxdebian

1 version

8.0

Application

drupaldrupal

≥ 8.6.0 && < 8.6.13

range

fedorafedoraproject

2 versions

2829

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 7.65.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-6341 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

O3 Security · Impact-Aware SCA

Is CVE-2019-6341 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works