How severe is CVE-2020-15231?

CVE-2020-15231 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-2020-15231?

CVE-2020-15231 affects the following packages: org.mapfish.print:print-lib (Maven), org.mapfish.print:print-servlet (Maven), org.mapfish.print:print-standalone (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-15231?

Update org.mapfish.print:print-lib to 3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-15231 is resolved across your whole dependency graph.

How do I detect CVE-2020-15231 in my Maven dependencies?

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

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

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

CVE-2020-15231 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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-2020-15231?

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

CVE-2020-15231 was published on October 2, 2020 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.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2020-15231 — print-lib

MEDIUMFix: mapfish/mapfish-print#1397

CVE-2020-15231 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.mapfish.print:print-lib. A fix is available for org.mapfish.print:print-lib — see the affected versions and patch details below.

XSS in Mapfish Print relating to JSONP support

Also known asGHSA-w534-q4xf-h5v2

Published

Oct 2, 2020

Updated

Oct 20, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

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

3 pkgs affected

☕org.mapfish.print:print-lib☕org.mapfish.print:print-servlet☕org.mapfish.print:print-standalone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A user can use the JSONP support to do a Cross-site scripting.

Patches

Use version >= 3.24

Workarounds

References

For more information

If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.mapfish.print:print-lib`	all versions	3.24`org.mapfish.print:print-lib:3.24`
☕Maven	`org.mapfish.print:print-servlet`	all versions	3.24`org.mapfish.print:print-servlet:3.24`
☕Maven	`org.mapfish.print:print-standalone`	all versions	3.24`org.mapfish.print:print-standalone:3.24`

Affected Products

1 product · 1 configurations

Application

printmapfish

< 3.24

range

Detection & mitigation playbook

Open-source dependency

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

### Impact A user can use the JSONP support to do a Cross-site scripting. ### Patches Use version >= 3.24 ### Workarounds No ### References * https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e * https://cwe.mitre.org/data/definitions/79.html ### For more information If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397