Security readout for executives and security teams
Plain-English summary
A WordPress plugin used to add Elementor templates can be abused through cross-site request forgery. An attacker would need to trick a logged-in site administrator into clicking or performing an action. Successful abuse could change or add form action metadata, creating integrity risk but not direct data theft or service outage based on the supplied sources.
Executive priority
Treat this as a routine but time-bound WordPress plugin update. The issue needs administrator interaction and has limited documented impact, but public websites with many administrators should patch promptly to reduce social-engineering exposure.
Technical view
CVE-2024-0511 is a CWE-352 CSRF issue in Royal Elementor Addons and Templates up to and including 1.3.87. The wpr_update_form_action_meta function lacks proper nonce validation. The CVSS 3.1 score is 4.3, with network attack vector, no privileges required, required user interaction, and low integrity impact.
Likely exposure
Exposure is limited to WordPress sites running Royal Elementor Addons and Templates versions up to 1.3.87, especially where administrators browse while authenticated. Sites without this plugin, or on versions newer than the affected range, are not indicated as affected by the supplied sources.
Exploitation context
The supplied sources do not show active exploitation, and the CVE is not listed as KEV. Abuse requires social engineering of an authenticated administrator, such as getting them to click a crafted link. The documented impact is unauthorized metadata posting, not code execution.
Researcher notes
The affected function is wpr_update_form_action_meta, with missing or incorrect nonce validation. The source bundle indicates versions through 1.3.87 are vulnerable and references a WordPress Trac changeset from 1.3.87 to 1.3.88. No supplied evidence supports active exploitation or broader impact.
Mitigation direction
- Inventory WordPress sites for Royal Elementor Addons and Templates installations.
- Upgrade affected plugin versions beyond 1.3.87 where available.
- Review the WordPress Trac 1.3.88 changeset and vendor guidance before deployment.
- Restrict administrator browsing from logged-in WordPress sessions where practical.
- Monitor WordPress admin activity for unexpected form action metadata changes.
Validation and detection
- Check each site’s installed plugin version against the affected range.
- Confirm the plugin is updated past 1.3.87 after remediation.
- Review administrative audit logs for unexpected metadata changes.
- Verify CSRF protections or nonce validation exist around affected form metadata updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-0511 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/dc8bef03-51e0-4448-bddd-85300104e875?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3026824%40royal-elementor-addons%2Ftags%2F1.3.87&new=3032004%40royal-elementor-addons%2Ftags%2F1.3.88CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.