WordPress security changelog
MEDIUM CVE-2024-1375 Deferred

Event post: A security weakness

Event post is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Event post
Plugin slug
event-post
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jul 12, 2024
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Jul 12, 2024 and is one of 14 known issues for this plugin.

Update, patch or deactivate.

No fixed release is identified. Update Event post when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Event post plugin for WordPress is vulnerable to unauthorized bulk metadata update due to a missing nonce check on the save_bulkdatas function in all versions up to, and including, 5.9.10. This makes it possible for unauthenticated attackers to update post_meta_data via a forged request, granted they can trick a logged-in user into performing an action such as clicking on a link.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Primary and upstream sources