CalendarWordPress extension · Kieranoshea
CVE-2013-2698
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 · uneditedCross-site request forgery (CSRF) vulnerability in the Calendar plugin before 1.3.3 for WordPress allows remote attackers to hijack the authentication of users for requests that add a calendar entry via unspecified vectors.
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 confidenceCross-site request forgery (CSRF) vulnerability in the Calendar plugin before version 1.3.3 for WordPress allows remote attackers to add calendar entries by tricking authenticated users into submitting malicious requests, hijacking their session authentication.
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
CalendarWordPress extension
<= 1.3.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Check Calendar plugin version in WordPress adminNavigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate the 'Calendar' plugin by Kieranoshea and note the version number displayed.Affected if The installed version is 1.3.2 or lower.
-
Verify plugin is activeIn the same Plugins screen, confirm whether the Calendar plugin shows as 'Active' rather than 'Inactive' or 'Not Installed'.Affected if The plugin is active and the version is 1.3.2 or lower.
-
Inspect plugin file header for versionAccess the plugin directory via FTP or file manager. Open the main plugin file (typically calendar.php or similar main file in the /wp-content/plugins/calendar/ directory) and locate the Version header comment at the top of the file.Affected if The Version field in the file header reads 1.3.2 or lower.
-
Check for CSRF protection in form handlingExamine the plugin PHP files for form submission handlers. Look for the presence of nonce validation or token checking when calendar entries are submitted. Search for functions handling admin-post.php or front-end form submissions.Affected if No nonce verification or CSRF token checks are found in form handling code, and the version is 1.3.2 or lower.
You are affected if the Calendar plugin is active at version 1.3.2 or lower and lacks anti-CSRF token protection in its form submission logic.
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 WordPress Calendar plugin to version 1.3.3 or later, which should include anti-CSRF token protection for form submissions.
Fix this in Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2698 — 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-2698 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