CVE-2016-6854 json
An issue was discovered in Open-Xchange OX Guard before 2.4.2-rev5.
published 2016-12-15 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7739
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered in Open-Xchange OX Guard before 2.4.2-rev5. Script code which got injected to a mail with inline PGP signature gets executed when verifying the signature. Malicious script code can be executed within a user's context. This can lead to session hijacking or triggering unwanted actions via the web interface (sending mail, deleting data etc.).
Timeline
- First public exploit (EDB-40377)
- Published
Exploit prediction
2.44% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-40377 Open-Xchange Guard 2.4.2 - Multiple Cross-Site Scripting Vulnerabilities webapps, 2016-09-13
- packetstormsecurity.com http://packetstormsecurity.com/files/138701/Open-Xchange-Guard-2.4.2-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| 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
-
exploit-db.com
/exploits/40377/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/138701/Open-Xchange-Guard-2.4.2-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/92920
vdb-entry, third-party-advisory
-
securityfocus.com
/archive/1/539395/100/0/threaded
mailing-list
Sources
- CVE List CVE-2016-6854
- NVD CVE-2016-6854
Fencer Vulns 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.