dbcve.org
Event Calendar WdWordPress extension · Web Dorado

CVE-2018-16164

MEDIUM · 5.4 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to after 1.1.21 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 version 1.1.21 and earlier allows remote authenticated 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 · high confidence

Cross-site scripting (XSS) vulnerability in Event Calendar WD WordPress plugin versions 1.1.21 and earlier allows authenticated users to inject arbitrary JavaScript or HTML into the application via unsanitized input fields.

MitigationUpgrade Event Calendar WD to a version newer than 1.1.21; if no update is available, implement output encoding and input validation on all user-supplied data within the plugin.

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.1.21

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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. Check if Event Calendar WD is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Event Calendar WD' or 'Event Calendar WD' in the plugin list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version
    In the plugins list, locate the version number displayed beneath the Event Calendar WD plugin name, or open the main plugin file (event-calendar-wd.php) and find the 'Version' header in the plugin comments
    Affected if The version is 1.1.21 or earlier (any version number equal to or lower than 1.1.21)
  3. Confirm user authentication is possible
    Check WordPress general settings to see if 'Anyone can register' is enabled, or verify that user accounts exist in the wp_users database table
    Affected if The site allows user registration or has existing registered users (including subscribers)

You are affected if Event Calendar WD version 1.1.21 or earlier is installed on your WordPress site and authenticated users can access the plugin's input fields

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.1.21
Interim mitigation

Upgrade Event Calendar WD to a version newer than 1.1.21; if no update is available, implement output encoding and input validation on all user-supplied data within the plugin.

Fix this in Event Calendar Wd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-16164 — 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-2018-16164 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