CVE-2018-17996 json
LayerBB before 1.1.3 allows CSRF for adding a user via admin/new_user.php, deleting a user via admin/members.php/delete_user/, and deleting…
published 7y ago modified 4mo ago also EUVD-2018-9735
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
LayerBB before 1.1.3 allows CSRF for adding a user via admin/new_user.php, deleting a user via admin/members.php/delete_user/, and deleting content via mod/delete.php/.
Patch / fix
Is CVE-2018-17996 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-46379)
- Published
Exploit prediction
3.01% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46379 LayerBB 1.1.2 - Cross-Site Request Forgery (Add Admin) webapps, 2019-02-14
- packetstormsecurity.com http://packetstormsecurity.com/files/151694/LayerBB-1.1.2-Cross-Site-Request-Forgery.html referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/AndyRixon/LayerBB/issues/38 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/AndyRixon/LayerBB/commits/master
patch, third-party-advisory
-
exploit-db.com
/exploits/46379/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/151694/LayerBB-1.1.2-Cross-Site-Request-Forgery.html
exploit, third-party-advisory, vdb-entry
-
github.com
/AndyRixon/LayerBB/issues/38
exploit, third-party-advisory
Sources
- CVE List CVE-2018-17996
- NVD CVE-2018-17996
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.