Modern Events Calendar LiteWordPress extension · Webnus
CVE-2024-5441
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 Modern Events Calendar plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the set_featured_image function in all versions up to, and including, 7.11.0. This makes it possible for authenticated attackers, with subscriber access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. The plugin allows administrators (via its settings) to extend the ability to submit events to unauthenticated users, which would allow unauthenticated attackers to exploit this vulnerability.
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 confidenceThe Modern Events Calendar WordPress plugin up to version 7.11.0 lacks file type validation in the set_featured_image function, allowing authenticated users with subscriber-level access or higher to upload arbitrary files to the server. When administrators enable the plugin's setting to allow unauthenticated event submissions, this vulnerability becomes exploitable by unauthenticated attackers, potentially leading to remote code execution.
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.5.6< 7.12.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed plugin versionCheck the WordPress plugin directory or wp-admin plugins list for 'Modern Events Calendar' version number. Compare against affected ranges: Lite <= 6.5.6 or Premium < 7.12.0Affected if Installed version is 6.5.6 or lower for Lite, or below 7.12.0 for premium version
-
Verify unauthenticated submission settingNavigate to plugin settings in WordPress admin: Modern Events Calendar > Settings > Event Submission > 'Allow Guest Submission' or similar option. Check if enabled.Affected if Unauthenticated/guest event submission is enabled in plugin settings
-
Confirm user registration statusIn WordPress admin, go to Settings > General > 'Membership' section. Check if 'Anyone can register' is enabled and note the default role (subscriber or higher)Affected if Anyone can register is enabled, allowing creation of subscriber-level accounts
-
Check for existing malicious uploadsInspect the WordPress media library and upload directories (typically wp-content/uploads/) for unexpected file types such as .php, .phtml, or .exe files that may have been uploadedAffected if Suspicious executable files found in upload directories that were not intentionally uploaded by administrators
Environment is affected if the plugin version is vulnerable AND either unauthenticated submission is enabled OR user registration allows subscriber-level account creation, allowing arbitrary file upload leading to potential remote code execution.
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 · scoped7.12.0
Update the Modern Events Calendar plugin to version 7.12.0 or later which includes proper file type validation. If immediate patching is not possible, disable the unauthenticated event submission feature in plugin settings and restrict user registration.
Modern Events Calendar version 7.12.0 or later
- 1. Create a full backup of the WordPress site (database and files) before making any changes
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Locate the Modern Events Calendar (or Modern Events Calendar Lite) plugin
- 4. If an update is available, click 'Update Now' to upgrade to version 7.12.0 or later
- 5. Alternatively, navigate to Dashboard > Updates and select the Modern Events Calendar plugin for update
- 6. After updating, verify the plugin version shows 7.12.0 or newer in the plugins list
- 7. Review the site's uploads directory (/wp-content/uploads/) for any suspicious files that may have been uploaded before the patch
- 8. Consider reviewing user accounts, especially those with 'subscriber' role, for any unauthorized access
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Modern Events Calendar Lite
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5441 — 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-2024-5441 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