An issue was discovered in phpMyAdmin.
An issue was discovered in phpMyAdmin. When the user does not specify a blowfish_secret key for encrypting cookies, phpMyAdmin generates one at runtime. A vulnerability was reported where the way this value is created uses a weak algorithm. This could allow an attacker to determine the user's blowfish_secret and potentially decrypt their cookies. All 4.6.x versions (prior to 4.6.5), 4.4.x versions (prior to 4.4.15.9), and 4.0.x versions (prior to 4.0.10.18) are affected.
- Published
- Dec 10, 2016
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 80th percentile
- CWE
- CWE-310
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| phpmyadmin | phpmyadmin | cpe:2.3:a:phpmyadmin:phpmyadmin |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phpmyadmin phpmyadmin4.0.0
- phpmyadmin phpmyadmin4.0.1
- phpmyadmin phpmyadmin4.0.10
- phpmyadmin phpmyadmin4.0.10.1
- phpmyadmin phpmyadmin4.0.10.10
- phpmyadmin phpmyadmin4.0.10.11
- phpmyadmin phpmyadmin4.0.10.12
- phpmyadmin phpmyadmin4.0.10.13
- phpmyadmin phpmyadmin4.0.10.14
- phpmyadmin phpmyadmin4.0.10.15
- phpmyadmin phpmyadmin4.0.10.16
- phpmyadmin phpmyadmin4.0.10.17
- phpmyadmin phpmyadmin4.0.10.2
- phpmyadmin phpmyadmin4.0.10.3
- phpmyadmin phpmyadmin4.0.10.4
- phpmyadmin phpmyadmin4.0.10.5
- phpmyadmin phpmyadmin4.0.10.6
- phpmyadmin phpmyadmin4.0.10.7
- phpmyadmin phpmyadmin4.0.10.8
- phpmyadmin phpmyadmin4.0.10.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.2 | phpmyadmin | before 4.4.15.9-r0 | 4.4.15.9-r0 |
| Alpine:v3.4 | phpmyadmin | before 4.6.5.2-r0 | 4.6.5.2-r0 |
| Debian:12 | phpmyadmin | before 4:4.6.5.1-1 | 4:4.6.5.1-1 |
| Packagist | phpmyadmin/phpmyadmin | from 4.0 · before 4.0.10.18 | 4.0.10.18 |
| Packagist | phpmyadmin/phpmyadmin | from 4.4 · before 4.4.15.9 | 4.4.15.9 |
| Packagist | phpmyadmin/phpmyadmin | from 4.6 · before 4.6.5 | 4.6.5 |
Same product
phpmyadmin: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-1151Static code injection vulnerability in setup.php in phpMyAdmin 2.11.x before 2.11.9.5 and 3.x before 3.1.3.1 allows remote attackers to injeKEV98Now
- CVE-2018-12613An issue was discovered in phpMyAdmin 4.8.x before 4.8.2, in which an attacker can include (view and potentially execute) files on the serve65This week
- CVE-2016-5734phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not properly choose delimiters to prevent use of the p63This week
- CVE-2020-26935An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3.59Plan
- CVE-2012-5159phpMyAdmin 3.5.2.2, as distributed by the cdnetworks-kr-1 mirror during an unspecified time frame in 2012, contains an externally introduced52Plan
- CVE-2020-5504In phpMyAdmin 4 before 4.9.4 and 5 before 5.0.1, SQL injection exists in the user accounts page.47Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:phpmyadmin | 4.4.15.9-r0 · Alpine:v3.2 | Package registry (OSV) |
| debian:phpmyadmin | 4:4.6.5.1-1 · Debian:12 | Package registry (OSV) |
| Packagist:phpmyadmin/phpmyadmin | 4.0.10.18 | Package registry (OSV) |
| Packagist:phpmyadmin/phpmyadmin | 4.4.15.9 | Package registry (OSV) |
| Packagist:phpmyadmin/phpmyadmin | 4.6.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.securityfocus.com/bid/94524
- security.gentoo.org/glsa/201701-32
- www.phpmyadmin.net/security/PMASA-2016-58
Vendor advisories and official records. Exploit/PoC links are deliberately left out.