Skip to content
Fencer Intel
medium 4.3

CVE-2013-1880 json

Apache ActiveMQ Cross-site scripting (XSS) vulnerability in the Portfolio publisher servlet

published 12y ago modified 4mo ago also GHSA-c9gx-27hq-wcvj , EUVD-2022-3548

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.8%
EPSS 6.8% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

Cross-site scripting (XSS) vulnerability in the Portfolio publisher servlet in the demo web application in Apache ActiveMQ before 5.9.0 allows remote attackers to inject arbitrary web script or HTML via the refresh parameter to demo/portfolioPublish, a different vulnerability than CVE-2012-6092.

Patch / fix

  • maven org.apache.activemq:activemq-core 5.9.0

Is CVE-2013-1880 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-1880 updated cvss 4.3

ActiveMQ: XSS vulnerability in portfolioPublish demo application

  • Red Hat Fuse MQ Enterprise 7.1.0
    fixed: vendor fix RHSA-2013:1029
  • Red Hat OpenShift Enterprise 1 activemq
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.79% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • issues.apache.org https://issues.apache.org/jira/browse/AMQ-4398 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.activemq:activemq-core
<5.9.0
5.9.0

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.