CVE-2009-4781 json
TUKEVA Password Reminder before 1.0.0.4 uses a hard-coded password for rem.accdb, which allows local users to discover credentials via a DB…
published 16y ago modified 4mo ago also EUVD-2009-4744
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 1
- Exploit-DB
Summary
TUKEVA Password Reminder before 1.0.0.4 uses a hard-coded password for rem.accdb, which allows local users to discover credentials via a DBI connection.
Is CVE-2009-4781 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-10201)
- Published
Exploit prediction
0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-10201 TEKUVA - Password Reminder Authentication Bypass local, 2009-11-21
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
exploit-db.com
/exploits/10201
exploit
-
secunia.com
/advisories/37553
third-party-advisory, vendor-advisory
-
tekuva.com
/index.php?option=com_docman&task=doc_details&gid=40&Itemid=9
url-repurposed
Sources
- CVE List CVE-2009-4781
- NVD CVE-2009-4781
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.