CVE-2015-6733 json
GeSHi, as used in the SyntaxHighlight_GeSHi extension and MediaWiki before 1.23.10, 1.24.x before 1.24.3, and 1.25.x before 1.25.2, allows…
published 2015-09-01 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-6671
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
GeSHi, as used in the SyntaxHighlight_GeSHi extension and MediaWiki before 1.23.10, 1.24.x before 1.24.3, and 1.25.x before 1.25.2, allows remote attackers to cause a denial of service (resource consumption) via unspecified vectors.
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-2015-6733 updated cvss 4.3
mediawiki: multiple security fixes in 1.25.2, 1.24.3, 1.23.10
-
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
2.75% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
security.gentoo.org
/glsa/201510-05
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2015-August/165193.html
vendor-advisory
-
lists.wikimedia.org
/pipermail/mediawiki-announce/2015-August/000179.html
mailing-list, vendor-advisory
-
openwall.com
/lists/oss-security/2015/08/27/6
mailing-list
-
openwall.com
/lists/oss-security/2015/08/12/6
mailing-list
- phabricator.wikimedia.org /T101608
-
securityfocus.com
/bid/76361
vdb-entry
Sources
- CVE List CVE-2015-6733
- NVD CVE-2015-6733
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.