How severe is CVE-2014-5191?

No CVSS score has been assigned to CVE-2014-5191 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-5191?

CVE-2014-5191 affects the following packages: ckeditor/ckeditor (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2014-5191?

Update ckeditor/ckeditor to 4.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-5191 is resolved across your whole dependency graph.

How do I detect CVE-2014-5191 in my Packagist dependencies?

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

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

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

CVE-2014-5191 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th 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-2014-5191?

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

CVE-2014-5191 was published on August 7, 2014 and was last updated on April 10, 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

CVE-2014-5191 — ckeditor

Fix: ckeditor/ckeditor4@b685874

CVE-2014-5191 is a Cross-site Scripting (XSS) vulnerability in ckeditor/ckeditor. A fix is available for ckeditor/ckeditor — see the affected versions and patch details below.

The Preview plugin in CKEditor allows Cross-site scripting (XSS)

Also known asGHSA-v27h-j97p-wqmx

Published

Aug 7, 2014

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘ckeditor/ckeditor

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

Cross-site scripting (XSS) vulnerability in the Preview plugin before 4.4.3 in CKEditor allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ckeditor/ckeditor`	all versions	4.4.3`composer require ckeditor/ckeditor:^4.4.3`

Affected Products

1 product · 3 configurations

Application

ckeditorckeditor

≤ 4.4.2

2 versions

4.4.04.4.1

Detection & mitigation playbook

Open-source dependency

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

Cross-site scripting (XSS) vulnerability in the Preview plugin before 4.4.3 in CKEditor allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.