How severe is CVE-2016-6810?

CVE-2016-6810 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-2016-6810?

CVE-2016-6810 affects the following packages: org.apache.activemq:activemq-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-6810?

Update org.apache.activemq:activemq-client to 5.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6810 is resolved across your whole dependency graph.

How do I detect CVE-2016-6810 in my Maven dependencies?

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

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

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

CVE-2016-6810 has an EPSS (Exploit Prediction Scoring System) score of 6.1%, placing it in the 93th 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-2016-6810?

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

CVE-2016-6810 was published on January 10, 2018 and was last updated on October 24, 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-2016-6810 — activemq-client

MEDIUMFix: apache/activemq@77b827f

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

Improper Neutralization of Input During Web Page Generation Apache ActiveMQ

Also known asGHSA-5jg4-p78r-p5j3

Published

Jan 10, 2018

Updated

Oct 24, 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 ↗

6.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% 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-client

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.x before 5.14.2, an instance of a cross-site scripting vulnerability was identified to be present in the web based administration console. The root cause of this issue is improper user data output validation.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:activemq-client`	≥ 5.0.0&&< 5.14.2	5.14.2`org.apache.activemq:activemq-client:5.14.2`

Affected Products

1 product · 1 configurations

Application

activemqapache

≥ 5.0.0 && < 5.14.2

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.apache.activemq:activemq-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.activemq:activemq-client to 5.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6810 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

O3 Security · Impact-Aware SCA

Is CVE-2016-6810 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works