ActivemqApplication · Apache
CVE-2016-6810
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache ActiveMQ 5.x before 5.14.2 contains a stored cross-site scripting (XSS) vulnerability in its web-based administration console due to improper output validation of user-supplied data. An attacker could inject malicious JavaScript code that executes in the context of other users accessing the admin console.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ActivemqApplication
>= 5.0.0, < 5.14.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Apache ActiveMQ versionCheck the version file in the ActiveMQ installation directory, typically found in a VERSION.txt or manifest file. You can also check the 'activemq-all' JAR file name or run 'activemq --version' if available in the bin directory.Affected if The installed version is 5.x and is lower than 5.14.2
-
Determine if the web-based administration console is enabledInspect the ActiveMQ configuration file (activemq.xml) and look for the jetty web console configuration. Check if the web console port (default 8161) is open and accessible on the network.Affected if The web administration console is enabled and accessible over the network
-
Verify the web console is reachableAttempt to access the ActiveMQ web console by navigating to http://hostname:8161/admin/ or http://hostname:8161/index.html in a web browser or using curl.Affected if The web console returns a valid login page or dashboard, confirming it is active
-
Check for suspicious stored content in the consoleLog into the web administration console and inspect any user-configurable fields such as topics, queues, or advisory message content for unexpected script tags or HTML elements.Affected if Unexpected script tags or HTML attributes are found in any user-controlled fields within the console
You are affected if your Apache ActiveMQ version is 5.x before 5.14.2 AND the web-based administration console is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.14.2
Upgrade to Apache ActiveMQ version 5.14.2 or later. Until upgrade is possible, restrict access to the administration console to trusted users only and implement web application firewall rules to detect and block XSS payloads.
Fix this in Activemq
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-6810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data