NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

Evolution CMS Cross-site Scripting (XSS)GHSA-9mfc-gr8c-xj4m

MEDIUMFix: evolution-cms/evolution@b59d1f5

GHSA-9mfc-gr8c-xj4m is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in evolutioncms/evolution. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for evolutioncms/evolution — see the affected versions and patch details below.

Also known asCVE-2018-16638
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk
0.00%0.36%0.72%1.08%0.2%0.6%May 26Sep 26Nov 26

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
🐘evolutioncms/evolution

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

Evolution CMS 1.4.x prior to 1.4.6 allows XSS via the manager/ search parameter.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistevolutioncms/evolution≥ 1.4.0&&< 1.4.61.4.6composer require evolutioncms/evolution:^1.4.6

Affected Products

1 product · 1 configurations
Application
evolution cmsmodx
≥ 1.4.0 && ≤ 1.4.7
range
Exploits & PoCs
1

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

Evolution CMS 1.4.x allows XSS via the manager/ search parameter.

github.comNVDFeb 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update evolutioncms/evolution to 1.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9mfc-gr8c-xj4m is resolved across your whole dependency graph.

  3. 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

Evolution CMS 1.4.x prior to 1.4.6 allows XSS via the manager/ search parameter.
O3 Security · Impact-Aware SCA

Is GHSA-9mfc-gr8c-xj4m in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Evolution CMS Cross-site Scripting (XSS) (Medium 5.4)