CVE-2011-2083 json
Multiple cross-site scripting (XSS) vulnerabilities in Best Practical Solutions RT 3.x before 3.8.12 and 4.x before 4.0.6 allow remote atta…
published 2012-06-04 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2077
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in Best Practical Solutions RT 3.x before 3.8.12 and 4.x before 4.0.6 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.
Patch / fix
- request-tracker4 Debian 12 4.0.5-3
debian advisories DEBIAN-CVE-2011-2083
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-2011-2083 updated cvss 6.8
rt3: Multiple security flaws fixed in upstream v3.8.12 and v4.0.6 versions
-
Red Hat All currently supported Red Hat productsnot 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
1.83% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
lists.bestpractical.com
/pipermail/rt-announce/2012-May/000203.html
mailing-list, patch
-
lists.bestpractical.com
/pipermail/rt-announce/2012-May/000204.html
mailing-list, patch
-
lists.bestpractical.com
/pipermail/rt-announce/2012-May/000202.html
mailing-list, patch, vendor-advisory
-
secunia.com
/advisories/49259
third-party-advisory
-
securityfocus.com
/bid/53660
vdb-entry
Sources
- CVE List CVE-2011-2083
- NVD CVE-2011-2083
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.