CVE-2014-10382 json
The feature-comments plugin before 1.2.5 for WordPress has CSRF for featuring or burying a comment.
published 7y ago modified 4mo ago also EUVD-2014-1153
- cvss
- 4.3
- 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
The feature-comments plugin before 1.2.5 for WordPress has CSRF for featuring or burying a comment.
Patch / fix
- pippinsplugins featured_comments 1.2.5
Is CVE-2014-10382 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 FencerExploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
wordpress.org
/plugins/feature-comments/#developers
release-notes
Sources
- CVE List CVE-2014-10382
- NVD CVE-2014-10382
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.