ethitter WP-Print-Friendly up to 0.5.2 wp-print-friendly.php information disclosure
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability classified as problematic has been found in ethitter WP-Print-Friendly up to 0.5.2 (WordPress Plugin). This affects an unknown part of the file wp-print-friendly.php. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.
The weakness was shared 01/03/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2013-10007. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
By approaching the search of inurl:wp-print-friendly.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.5.3 eliminates this vulnerability. Applying the patch 437787292670c20b4abe20160ebbe8428187f2b4 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 5.3
CNA Vector (VulDB): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: WP-Print-Friendly 0.5.3
Timeline01/03/2023 Advisory disclosed
01/03/2023 +0 days CVE reserved
01/03/2023 +0 days VulDB entry created
01/27/2023 +24 days VulDB last update
CVE: CVE-2013-10007 (🔒)
EntryCreated: 01/03/2023 12:01 PM
Updated: 01/27/2023 10:41 AM
Changes: 01/03/2023 12:01 PM (42), 01/27/2023 10:35 AM (3), 01/27/2023 10:41 AM (28)
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!
No comments yet. Languages: en.
Please log in to comment.