dbcve.org
Event Calendar WdWordPress extension · Web Dorado

CVE-2017-2224

MEDIUM · 6.1 CVSS v3.0 Published 2017-07-07
Fix available
A fix is available. Upgrade to after 1.0.93 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site scripting vulnerability in Event Calendar WD prior to version 1.0.94 allows remote attackers to inject arbitrary web script or HTML 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 · moderate confidence

Event Calendar WD plugin before version 1.0.94 contains a cross-site scripting (XSS) vulnerability that allows remote attackers to inject arbitrary web script or HTML through unspecified vectors. The vulnerability likely involves insufficient input sanitization on user-supplied data that gets reflected in the plugin's output, allowing malicious scripts to execute in the context of other users' browsers.

MitigationUpgrade Event Calendar WD to version 1.0.94 or later. If immediate upgrade is not possible, implement web application firewall rules to filter malicious script tags and review the plugin's input handling code for proper output encoding.

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
Event Calendar WdWordPress extension
Affected:<= 1.0.93

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Event Calendar WD plugin is installed
    Locate the plugin in the WordPress plugin directory or check the file system for the Event Calendar WD plugin folder (typically in /wp-content/plugins/wd-calendar/ or similar).
    Affected if The plugin folder exists and contains Event Calendar WD files.
  2. Identify the installed version
    Check the plugin's main PHP file (often named index.php, wd-calendar.php, or similar) for a version constant or header comment. Alternatively, look in the WordPress plugins admin panel for the installed version number.
    Affected if The version is 1.0.93 or lower.
  3. Determine if the plugin is active and accessible
    Check if the plugin is enabled in WordPress admin and if the calendar front-end views are publicly accessible. Inspect the calendar shortcode or widget usage on the site.
    Affected if The plugin is active and calendar functionality is in use on the site.
  4. Review input fields for XSS vulnerability
    Inspect the calendar's user-facing forms (event submission, event details, calendar navigation) using browser developer tools. Identify all parameters that accept user input and get reflected in the output.
    Affected if User-supplied input in calendar fields (such as event titles, descriptions, or dates) can be submitted without proper encoding.
  5. Check server logs for XSS indicators
    Review web server access logs and application logs for suspicious requests containing script tags, HTML tags, or event handlers in parameters related to the calendar (such as ?event_id=, ?calendar_id=, or form submissions).

A user is affected if Event Calendar WD version 1.0.93 or lower is installed and the calendar functionality is active, allowing unfiltered user input to be reflected in output.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.93
Interim mitigation

Upgrade Event Calendar WD to version 1.0.94 or later. If immediate upgrade is not possible, implement web application firewall rules to filter malicious script tags and review the plugin's input handling code for proper output encoding.

Fix this in Event Calendar Wd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2224 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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