CVE-2020-7108 json
The LearnDash LMS plugin before 3.1.2 for WordPress allows XSS via the ld-profile search field.
published 6y ago modified 4mo ago also EUVD-2020-28242
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
The LearnDash LMS plugin before 3.1.2 for WordPress allows XSS via the ld-profile search field.
Patch / fix
- learndash learndash 3.1.2
Is CVE-2020-7108 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
- Published
- First public exploit (EDB-48030)
Exploit prediction
3.46% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-48030 WordPress Plugin LearnDash LMS 3.1.2 - Reflective Cross-Site Scripting webapps, 2020-02-10
- packetstormsecurity.com http://packetstormsecurity.com/files/156275/LearnDash-WordPress-LMS-3.1.2-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/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
-
packetstormsecurity.com
/files/156275/LearnDash-WordPress-LMS-3.1.2-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
-
learndash.releasenotes.io
/release/uCskc-version-312
release-notes, vendor-advisory
-
wpvulndb.com
/vulnerabilities/10026
third-party-advisory
-
getastra.com
/blog/911/plugin-exploit/reflected-xss-vulnerability-found-in-learndash-lms-plugin/
third-party-advisory
-
jinsonvarghese.com
/reflected-xss-in-learndash-wordpress-plugin/
third-party-advisory
Sources
- CVE List CVE-2020-7108
- NVD CVE-2020-7108
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.