CVE-2013-7137 in the critical feed json
The "remember me" functionality in login.php in Burden before 1.8.1 allows remote attackers to bypass authentication and gain privileges by…
published 12y ago modified 4mo ago also EUVD-2013-6920
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.1%
- EPSS 16.1% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
The "remember me" functionality in login.php in Burden before 1.8.1 allows remote attackers to bypass authentication and gain privileges by setting the burden_user_rememberme cookie to 1.
Patch / fix
- burden_project burden 1.8.1
Is CVE-2013-7137 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-30916)
- Published
Exploit prediction
16.08% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-30916 Burden 1.8 - Authentication Bypass webapps, 2014-01-14
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/joshf/Burden/commit/edaa1bb8f73d6f3c8b2e78b67f1b40e02fccd0c1
patch, third-party-advisory
-
github.com
/joshf/Burden/issues/2
issue-tracking, patch, third-party-advisory
-
exploit-db.com
/exploits/30916
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/archive/1/530703/100/0/threaded
mailing-list, broken-link, third-party-advisory, vdb-entry
-
github.com
/joshf/Burden/releases/tag/1.8.1
release-notes, third-party-advisory
-
htbridge.com
/advisory/HTB23192
broken-link
Sources
- CVE List CVE-2013-7137
- NVD CVE-2013-7137
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.