CVE-2018-10310 json
A persistent cross-site scripting vulnerability has been identified in the web interface of the Catapult UK Cookie Consent plugin before 2.…
published 8y ago modified 4mo ago also EUVD-2018-2384
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
A persistent cross-site scripting vulnerability has been identified in the web interface of the Catapult UK Cookie Consent plugin before 2.3.10 for WordPress that allows the execution of arbitrary HTML/script code in the context of a victim's browser.
Patch / fix
- catapultthemes cookie_consent 2.3.10
Is CVE-2018-10310 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 FencerTimeline
- First public exploit (EDB-44503)
- Published
Exploit prediction
3.74% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44503 UK Cookie Consent - Persistent Cross-Site Scripting webapps, 2018-04-24
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
exploit-db.com
/exploits/44503/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/147333/WordPress-UK-Cookie-Consent-2.3.9-Cross-Site-Scripting.html
third-party-advisory, vdb-entry
-
wordpress.org
/plugins/uk-cookie-consent/#developers
product, release-notes
-
gist.github.com
/B0UG/9732614abccaf2893c352d14c822d07b
third-party-advisory
Sources
- CVE List CVE-2018-10310
- NVD CVE-2018-10310
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.