CVE-2012-6313
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsimple-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Simple Gmail Login WordPress plugin before version 1.1.4 contains an information disclosure vulnerability in simple-gmail-login.php. When a request lacks the expected timezone parameter, the PHP script fails to handle the missing input gracefully and outputs a stack trace revealing the server's installation path.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Simple Gmail Login plugin fileNavigate to your WordPress wp-content/plugins directory and search for simple-gmail-login.php, or check via WordPress admin under Plugins > Installed PluginsAffected if The file simple-gmail-login.php exists in the plugins directory
-
Determine the installed plugin versionOpen simple-gmail-login.php and look for the plugin header comment containing 'Version:' or check the WordPress plugin admin page for the installed version numberAffected if The version listed is 1.1.2 or 1.1.3 (any version of these releases)
-
Verify if PHP error display is enabledCheck your php.ini file for 'display_errors = On' or create a PHP info page to check the current error reporting settingsAffected if display_errors is set to On (the stack trace would be visible to attackers)
-
Test for the missing timezone parameter behaviorSend a crafted request to the simple-gmail-login.php endpoint without the timezone parameter (e.g., via curl or browser), for example: https://yourdomain.com/wp-content/plugins/simple-gmail-login/simple-gmail-login.phpAffected if The response includes a PHP stack trace, error message, or reveals the server's file system path
You are affected if the Simple Gmail Login plugin version is 1.1.2 or 1.1.3 AND PHP display_errors is enabled, causing path disclosure when requests omit the timezone parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Simple Gmail Login plugin to version 1.1.4 or later, which includes proper error handling. Alternatively, disable PHP error display on the production server to prevent stack trace disclosure.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-6313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data