CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
The Portable phpMyAdmin plugin before 1.3.1 for WordPress allows remote attackers to bypass authentication and obtain phpMyAdmin console access via a direct request to wp-content/plugins/portable-phpmyadmin/wp-pma-mod.
Category : Permissions, Privileges, and Access Controls Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
7.5
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
7.03%
–
–
2022-04-03
–
–
7.03%
–
–
2022-05-29
–
–
6.46%
–
–
2022-07-17
–
–
6.46%
–
–
2022-09-04
–
–
6.03%
–
–
2022-12-04
–
–
4.98%
–
–
2023-02-26
–
–
4.98%
–
–
2023-03-12
–
–
–
3.53%
–
2023-03-26
–
–
–
3.34%
–
2023-07-09
–
–
–
2.81%
–
2023-10-29
–
–
–
2.81%
–
2024-01-14
–
–
–
2.26%
–
2024-02-04
–
–
–
2.26%
–
2024-02-11
–
–
–
1.17%
–
2024-03-17
–
–
–
1.28%
–
2024-06-02
–
–
–
1.17%
–
2024-06-02
–
–
–
1.17%
–
2024-09-22
–
–
–
1.36%
–
2024-10-06
–
–
–
1.36%
–
2024-12-22
–
–
–
1.92%
–
2025-01-12
–
–
–
1.68%
–
2025-02-02
–
–
–
1.68%
–
2025-03-09
–
–
–
1.01%
–
2025-01-19
–
–
–
1.68%
–
2025-02-02
–
–
–
1.68%
–
2025-03-09
–
–
–
1.01%
–
2025-03-18
–
–
–
–
4.11%
2025-03-30
–
–
–
–
3.38%
2025-04-15
–
–
–
–
3.38%
2025-04-15
–
–
–
–
3.38,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
Publication date : 2012-12-12 23h00 +00:00 Author : Mark Stanislav EDB Verified : Yes
'portable-phpMyAdmin (WordPress Plugin)' Authentication Bypass (CVE-2012-5469)
Mark Stanislav - mark.stanislav@gmail.com
I. DESCRIPTION
---------------------------------------
portable-phpMyAdmin doesn't verify an existing WordPress session (privileged or not) when accessing the plugin file path directly. Because of how this plugin works, a default installation will provide a full phpMyAdmin console with the privilege level of the MySQL configuration of WordPress.
II. TESTED VERSION
---------------------------------------
1.3.0
III. PoC EXPLOIT
---------------------------------------
Navigate to http://host/wp-content/plugins/portable-phpmyadmin/wp-pma-mod and you will be presented with the full portable-phpMyAdmin web interface without the requirement of a session or any credential.
IV. SOLUTION
---------------------------------------
Upgrade to version 1.3.1
V. REFERENCES
---------------------------------------
http://wordpress.org/extend/plugins/portable-phpmyadmin/
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5469
VI. TIMELINE
---------------------------------------
10/13/2012 - Initial developer disclosure
10/14/2012 - Response from developer with commitment to fix the vulnerability
10/31/2012 - Follow-up with developer after no communication or patched release
11/16/2012 - Second attempt to follow-up with developer regarding progress/timetable
11/26/2012 - Contacted WordPress 'plugins team' about lack of progress on patched release
11/27/2012 - WordPress 'plugins team' patches software and releases version 1.3.1
12/12/2012 - Public disclosure