Modern Events Calendar LiteWordPress extension · Webnus
CVE-2022-30533
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 scripting vulnerability in Modern Events Calendar Lite versions prior to 6.3.0 allows remote an authenticated attacker to inject an arbitrary script 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 confidenceCross-site scripting (XSS) vulnerability in Modern Events Calendar Lite WordPress plugin versions prior to 6.3.0 allows an authenticated attacker to inject arbitrary JavaScript scripts through unspecified vectors, likely via event data input fields. This stored XSS could execute in browsers of users viewing affected event 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
Modern Events Calendar LiteWordPress extension
< 6.3.0CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Modern Events Calendar Lite is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'Modern Events Calendar Lite' or 'MEC' in the plugin list. Alternatively, check the wp-content/plugins/ directory for a folder containing 'modern-events-calendar' or 'mec'.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin under Plugins > Installed Plugins, click on the plugin name to view details, or inspect the main plugin PHP file header (typically in wp-content/plugins/modern-events-calendar-lite/) for the 'Version' field. Compare this version number to 6.3.0.Affected if The installed version is lower than 6.3.0 (e.g., 6.2.9, 6.2.0, 5.x, etc.)
-
Verify if user registration or contributor access is enabledIn WordPress admin, go to Settings > General and check if 'Anyone can register' is enabled. Then navigate to Users to review accounts that have roles capable of creating events (such as Administrator, Editor, Author, or custom roles with event creation permissions).Affected if User registration is open or multiple users have event creation capabilities, providing attack surface for an authenticated attacker
-
Inspect event data for injected scriptsIn WordPress admin, navigate to Events (or MEC > Events) and review existing event entries. Check event titles, descriptions, location fields, and custom fields for unexpected script tags (<script>), javascript: URIs, or on* event handlers (onclick, onload, etc.).Affected if Stored malicious scripts are found in any event data fields, indicating the vulnerability has been exploited
A user is affected if Modern Events Calendar Lite version is below 6.3.0 AND the WordPress site allows users with event creation permissions (authenticated access), or if existing events already contain suspicious script injections.
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.
dbcve · scoped6.3.0
Update Modern Events Calendar Lite to version 6.3.0 or later to apply the vendor patch. If immediate update is not possible, restrict user registration and review user roles with event creation permissions.
Modern Events Calendar Lite 6.3.0 or later
- Backup your WordPress site database and files
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Modern Events Calendar Lite' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 6.3.0 or later
- Verify the update completed successfully
- Test the calendar functionality to ensure proper operation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Modern Events Calendar Lite
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30533 — 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-2022-30533 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