How severe is CVE-2020-1941?

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

CVE-2020-1941 affects the following packages: org.apache.activemq:activemq-web-console (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-1941?

Update org.apache.activemq:activemq-web-console to 5.15.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1941 is resolved across your whole dependency graph.

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

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

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

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

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

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

CVE-2020-1941 was published on May 14, 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-1941 — activemq-web-console

MEDIUMFix: apache/activemq@7793a95

CVE-2020-1941 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.apache.activemq:activemq-web-console. A fix is available for org.apache.activemq:activemq-web-console — see the affected versions and patch details below.

Apache ActiveMQ webconsole admin GUI is open to XSS

Also known asBIT-activemq-2020-1941GHSA-cc94-3v9c-7rm8

Published

May 14, 2020

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

7.1%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕org.apache.activemq:activemq-web-console

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

In Apache ActiveMQ 5.0.0 to 5.15.11, the webconsole admin GUI is open to XSS, in the view that lists the contents of a queue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:activemq-web-console`	≥ 5.0.0&&< 5.15.12	5.15.12`org.apache.activemq:activemq-web-console:5.15.12`

Affected Products

7 products · 14 configurations

Application

activemqapache

≥ 5.0.0 && ≤ 5.15.11

range

Application

communications diameter signaling routeroracle

≥ 8.0.0 && ≤ 8.2.2

range

Application

communications element manageroracle

3 versions

8.1.18.2.08.2.1

Application

communications session report manageroracle

3 versions

8.1.18.2.08.2.1

Application

communications session route manageroracle

3 versions

8.1.18.2.08.2.1

Application

enterprise repositoryoracle

1 version

11.1.1.7.0

Detection & mitigation playbook

Open-source dependency

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

In Apache ActiveMQ 5.0.0 to 5.15.11, the webconsole admin GUI is open to XSS, in the view that lists the contents of a queue.

O3 Security · Impact-Aware SCA

Is CVE-2020-1941 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2020-1941 — activemq-web-console

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-2020-1941 in your dependencies?