Simple Gmail Login 1.1.3 up to 1.1.3 Installation simple-gmail-login.php information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Simple Gmail Login 1.1.3 up to 1.1.3. Impacted is an unknown function of the file simple-gmail-login.php of the component Installation. Executing a manipulation can lead to information disclosure. This vulnerability appears as CVE-2012-6313. In addition, an exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in Simple Gmail Login 1.1.3 up to 1.1.3. It has been declared as problematic. This vulnerability affects an unknown part of the file simple-gmail-login.php of the component Installation. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:
simple-gmail-login.php in the Simple Gmail Login plugin before 1.1.4 for WordPress allows remote attackers to obtain sensitive information via a request that lacks a timezone, leading to disclosure of the installation path in a stack trace.
The weakness was presented 12/11/2012 (Website). The advisory is available at wordpress.org. This vulnerability was named CVE-2012-6313 since 12/06/2012. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:simple-gmail-login.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.1.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (38111). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: 1.1.3 1.1.4
Timeline
12/06/2012 🔍12/11/2012 🔍
12/11/2012 🔍
03/24/2015 🔍
06/22/2025 🔍
Sources
Advisory: wordpress.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2012-6313 (🔍)
GCVE (CVE): GCVE-0-2012-6313
GCVE (VulDB): GCVE-100-63178
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/24/2015 12:22Updated: 06/22/2025 10:27
Changes: 03/24/2015 12:22 (44), 02/06/2018 07:40 (6), 06/22/2025 10:27 (27)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.