How severe is CVE-2018-20757?

CVE-2018-20757 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-2018-20757?

CVE-2018-20757 affects the following packages: modx/revolution (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-20757?

Update modx/revolution to 2.7.1-pl or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-20757 is resolved across your whole dependency graph.

How do I detect CVE-2018-20757 in my Packagist dependencies?

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

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

Yes. There are 1 known exploit references for CVE-2018-20757, 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-2018-20757?

CVE-2018-20757 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 58th 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-2018-20757?

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

CVE-2018-20757 was published on February 6, 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-2018-20757 — revolution

MEDIUMFix: modxcms/revolution@489b13c

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

MODX Revolution allows XSS through extended user fields

Also known asGHSA-gm2g-65wj-43g8

Published

Feb 6, 2019

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 29, 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 CVEs58th percentile — riskier than 58% 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

🐘modx/revolution

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

MODX Revolution through v2.7.0-pl allows XSS via an extended user field such as a Container name or Attribute name.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`modx/revolution`	all versions	2.7.1-pl`composer require modx/revolution:^2.7.1-pl`

Affected Products

1 product · 2 configurations

Application

modx revolutionmodx

≤ 2.7.0

1 version

2.7.0

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.

MODX Revolution through v2.7.0-pl allows XSS via an extended user field …

github.comNVDFeb 2019

Detection & mitigation playbook

Open-source dependency

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

MODX Revolution through v2.7.0-pl allows XSS via an extended user field such as a Container name or Attribute name.

O3 Security · Impact-Aware SCA

Is CVE-2018-20757 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.

OpenSSF Scorecard

Package health score

revolution

5.8/10

Code-Review8/10

Maintained10/10

Branch-Protection5/10

Assessed Oct 26, 2026

Timeline

Disclosed

Feb 6, 2019

First exploit

Feb 6, 2019

Same day as disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2018-20757

GHSA-gm2g-65wj-43g8

References

Advisorynvd.nist.gov · CVE 2018 20757 Fixgithub.com Webgithub.com · 489b13c61673ea0b19124e18cf1f3e7673f8aa64 Packagegithub.com · revolution

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting modx/revolution are rated as high or higher (top: high).

CVE-2025-28010CVE-2017-9069CVE-2017-9070CVE-2017-9067CVE-2017-9071CVE-2017-1000067CVE-2017-9068CVE-2018-20756

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2018-20757 — revolution

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-2018-20757 in your dependencies?