CVE-2018-5123 json
A third party website can access information available to a user with access to a restricted bug entry using the image generation in report…
published 7y ago modified 4mo ago also EUVD-2018-16909
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
A third party website can access information available to a user with access to a restricted bug entry using the image generation in report.cgi in all Bugzilla versions prior to 4.4.
Patch / fix
Is CVE-2018-5123 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-5123 updated cvss 4.8
bugzilla: CSRF in report.cgi allows to extract confidential information from a bug
-
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
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.mozilla.org https://bugzilla.mozilla.org/show_bug.cgi?id=CVE-2018-5123 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Mozilla Bugzilla
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
bugzilla.mozilla.org
/show_bug.cgi?id=CVE-2018-5123
exploit, issue-tracking, patch, vendor-advisory
Sources
- CVE List CVE-2018-5123
- NVD CVE-2018-5123
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.