CVE-2013-1422
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 · uneditedwebcalendar before 1.2.7 shows the reason for a failed login (e.g., "no such user").
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 confidencewebcalendar before version 1.2.7 contains an information disclosure vulnerability in its login functionality. The application returns specific error messages (e.g., 'no such user') that reveal why authentication failed, allowing attackers to enumerate valid usernames by observing different error responses.
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 data< 1.2.7CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify the installed WebCalendar versionCheck the version file or admin interface - typically found in the version.php file, about.php page, or the system-settings area of the WebCalendar installationAffected if Version is lower than 1.2.7
-
Test login error message for non-existent usernameSubmit a login form with a username that definitely does not exist (e.g., 'nonexistentuser123') and any password. Record the exact error message returned.Affected if Error message specifically states 'no such user' or similar wording that confirms the username does not exist
-
Test login error message for valid username with wrong passwordSubmit the login form with a known-valid username (or one that might exist) and an incorrect password. Record the exact error message returned.Affected if Error message differs from the non-existent username message (e.g., states 'invalid password' or 'incorrect password' instead of 'no such user')
-
Compare error message specificityReview both error messages obtained from steps 2 and 3. Determine if they reveal whether the username is valid versus whether just the password is wrong.Affected if Error messages are distinct and allow an attacker to determine which credential (username or password) is incorrect
You are affected if WebCalendar version is below 1.2.7 AND the login page returns different error messages for invalid usernames versus incorrect passwords, enabling user enumeration.
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 data1.2.7
Upgrade webcalendar to version 1.2.7 or later, which implements generic error messages that do not disclose whether the username or password was incorrect.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1422 — 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-2013-1422 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