My CalendarWordPress extension · My Calendar Project
CVE-2019-15713
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 · uneditedThe my-calendar plugin before 3.1.10 for WordPress has XSS.
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 · moderate confidenceCross-Site Scripting (XSS) vulnerability in the my-calendar WordPress plugin versions prior to 3.1.10. An attacker could inject malicious scripts into the plugin's input fields that would execute in the browsers of other users viewing affected pages.
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
My CalendarWordPress extension
< 3.1.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 My Calendar plugin installation directoryCheck the WordPress plugins folder (wp-content/plugins/) for a folder named 'my-calendar' or 'my-calendar-project'. Alternatively, in the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'My Calendar' in the list.Affected if The plugin folder does not exist or the plugin is not listed in WordPress, indicating the plugin is not installed.
-
Identify the installed plugin versionIf using the WordPress admin: go to Plugins > Installed Plugins, find 'My Calendar', and view the version number under the plugin name. If accessing files directly: open the plugin's main PHP file (typically my-calendar.php or my-calendar/my-calendar.php) and locate the 'Version' header in the plugin comment block at the top of the file.Affected if The version displayed is blank, unreadable, or cannot be determined from the plugin files.
-
Verify the plugin statusIn WordPress admin, go to Plugins > Installed Plugins and check whether My Calendar shows as 'Active' or 'Inactive'. Alternatively, query the WordPress database options table for the option 'my_calendar_is_installed' or check if the plugin's database tables exist.Affected if The plugin is active and processing requests, meaning the vulnerable input fields are accessible to users.
-
Compare the installed version against the vulnerable rangeTake the version number identified in step 2 and compare it to 3.1.10. Any version less than 3.1.10 (such as 3.1.9, 3.1.8, 3.0.x, 2.x, etc.) falls within the vulnerable range.Affected if The installed version is less than 3.1.10 (for example, 3.1.9, 3.1.0, 2.5.4). Versions 3.1.10 and later are patched.
If the My Calendar plugin is installed, active, and running a version lower than 3.1.10, the environment is affected by this XSS vulnerability.
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 data3.1.10
Update my-calendar plugin to version 3.1.10 or later. If immediate update is not possible, consider disabling the plugin until the patch can be applied.
Fix this in My Calendar
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15713 — 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-2019-15713 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