How severe is CVE-2017-6927?

CVE-2017-6927 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-2017-6927?

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

How do I fix CVE-2017-6927?

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

How do I detect CVE-2017-6927 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-2017-6927 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-2017-6927 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-6927 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-2017-6927?

CVE-2017-6927 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 76th 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-2017-6927?

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

CVE-2017-6927 was published on March 1, 2018 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-2017-6927 — core

MEDIUM

CVE-2017-6927 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.

Drupal cross-site scripting vulnerability

Also known asGHSA-585j-5449-mf5m

Published

Mar 1, 2018

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

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

4 pkgs affected

🐘drupal/core🐘drupal/core🐘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

Drupal 8.4.x versions before 8.4.5 and Drupal 7.x versions before 7.57 has a Drupal.checkPlain() JavaScript function which is used to escape potentially dangerous text before outputting it to HTML (as JavaScript output does not typically go through Twig autoescaping). This function does not correctly handle all methods of injecting malicious HTML, leading to a cross-site scripting vulnerability under certain circumstances. The PHP functions which Drupal provides for HTML escaping are not affected.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.4.0&&< 8.4.5	8.4.5`composer require drupal/core:^8.4.5`
🐘Packagist	`drupal/core`	≥ 7.0&&< 7.57	7.57`composer require drupal/core:^7.57`
🐘Packagist	`drupal/drupal`	≥ 8.4.0&&< 8.4.5	8.4.5`composer require drupal/drupal:^8.4.5`
🐘Packagist	`drupal/drupal`	≥ 7.0&&< 7.57	7.57`composer require drupal/drupal:^7.57`

Affected Products

2 products · 5 configurations

debian linuxdebian

3 versions

7.08.09.0

Application

drupaldrupal

≥ 8.4.0 && < 8.4.5

range

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 8.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-6927 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-2017-6927 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, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

security-advisories

4.8/10

Maintained10/10

Code-Review10/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

Mar 1, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2017-6927

GHSA-585j-5449-mf5m

References

Advisorysecurityfocus.com Advisorylists.debian.org · msg00030 Advisorydebian.org · dsa 4123 Advisorydrupal.org · sa core 2018 001 Advisorynvd.nist.gov · CVE 2017 6927 Webgithub.com · CVE 2017 6927.yaml Webgithub.com · CVE 2017 6927.yaml Packagegithub.com · core

Related vulnerabilities

This CVE is medium severity; 5 of 8 other CVEs affecting drupal/core are rated as high or higher (top: critical).

CVE-2026-6365CVE-2026-9082CVE-2026-6367CVE-2026-6366CVE-2025-13080CVE-2025-13082CVE-2025-13081CVE-2025-13083

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026