Modern Events CalendarWordPress extension · Webnus
CVE-2024-6522
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 Server-Side Request Forgery in all versions up to, and including, 7.12.1 via the 'mec_fes_form' AJAX function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 contains an SSRF vulnerability in the 'mec_fes_form' AJAX function affecting all versions up to 7.12.1. Authenticated users with Subscriber-level permissions can make arbitrary web requests from the server, potentially accessing internal services and sensitive data.
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 CalendarWordPress extension
< 7.13.0
Modern Events Calendar LiteWordPress extension
< 7.13.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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.
-
Verify Modern Events Calendar plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Modern Events Calendar' or 'Modern Events Calendar Lite' in the list. Note whether it is active or inactive.Affected if The plugin (either paid or Lite version) is installed and active
-
Check installed plugin versionIn the Plugins list, click on the plugin name to view details, or check the plugin's main PHP file header for the 'Version' field. Compare the version number against the affected range.Affected if The installed version is prior to 7.13.0 (e.g., 7.12.1, 7.11.0, etc.)
-
Confirm the vulnerable AJAX endpoint existsCheck the plugin files for the 'mes_fes_form' AJAX action handler. This is typically registered in the plugin's main file using add_action('wp_ajax_mec_fes_form', ...) or similar. Inspect the code to confirm the endpoint handles user-supplied URLs.Affected if The 'mec_fes_form' AJAX action exists in the plugin code and processes URL parameters without proper validation
-
Identify users with Subscriber-level accessIn WordPress admin, go to Users and review user roles. Subscribers have the lowest privilege level but are able to make AJAX requests. Check if any subscriber-level user accounts exist on the site.Affected if There is at least one user with the Subscriber role (or any authenticated user) who can access the site's AJAX functionality
You are affected if the Modern Events Calendar plugin (full or Lite) is installed with a version lower than 7.13.0, the vulnerable 'mec_fes_form' AJAX endpoint is present, and any authenticated user with Subscriber-level permissions exists on the site.
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.13.0
Update the Modern Events Calendar plugin to version 7.12.2 or later. If no update is available, disable the plugin or implement server-level restrictions on the AJAX endpoint to prevent unauthorized access.
Modern Events Calendar and Modern Events Calendar Lite 7.13.0
- 1. Backup your WordPress database and files before updating
- 2. Navigate to Plugins > Installed Plugins in WordPress admin
- 3. Find Modern Events Calendar (or Modern Events Calendar Lite) in the plugin list
- 4. If an update is available, click 'Update Now' to update to version 7.13.0
- 5. Alternatively, download version 7.13.0 from wordpress.org or the vendor and upload manually
- 6. Verify the update was successful by checking the installed version number
- 7. Test that the plugin functionality works normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Modern Events Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6522 — 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-6522 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