LiveActive security incident?Get immediate response
CVE Record

CVE-2024-0516: Royal Elementor Addons and Templates <= 1.3.87 - Missing Authorization via wpr_update_form_action_meta

The Royal Elementor Addons and Templates plugin for WordPress is vulnerable to unauthorized post metadata update due to a missing capability check on the wpr_update_form_action_meta function in all versions up to, and including, 1.3.87. This makes it possible for unauthenticated attackers to update certain metadata.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-0516 affects the Royal Elementor Addons and Templates WordPress plugin. A missing authorization check could let an unauthenticated internet attacker change certain post metadata. The known impact is integrity loss, not data theft or service outage. Public sources do not show CISA KEV listing or confirmed active exploitation.

Executive priority

Treat this as a timely WordPress hygiene issue, not a crisis. Prioritize exposed production sites and marketing sites because unauthenticated changes to content metadata can affect trust, content integrity, and operations.

Technical view

The vulnerable function is wpr_update_form_action_meta in Royal Elementor Addons and Templates versions up to and including 1.3.87. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, score 5.3. The bundled record maps it to CWE-352 and references the WordPress plugin changeset from 1.3.87 to 1.3.88.

Likely exposure

Exposure is likely limited to WordPress sites running Royal Elementor Addons and Templates at version 1.3.87 or older. Internet-facing WordPress sites are the main concern because the source states unauthenticated attackers can update certain metadata.

Exploitation context

The source bundle does not provide proof of exploitation, payload details, or CISA KEV status. The risk comes from unauthenticated network reachability and low attack complexity, balanced by the described impact being limited to certain metadata integrity changes.

Researcher notes

Evidence is enough to identify affected software, vulnerable version range, vulnerable function, and likely fixed release boundary. The bundle does not define exactly which metadata keys can be changed or provide confirmed exploitation status, so validation should focus on versioning and integrity review.

Mitigation direction

  • Inventory WordPress sites using Royal Elementor Addons and Templates.
  • Update the plugin to a release newer than 1.3.87 after verifying vendor guidance.
  • If upgrade is delayed, disable the plugin where business allows.
  • Monitor for unexpected post metadata changes on affected sites.
  • Review Wordfence and WordPress plugin advisories for updated guidance.

Validation and detection

  • Confirm each site’s installed plugin version is newer than 1.3.87.
  • Check whether any public WordPress sites still run the plugin.
  • Review post metadata audit trails or backups for unexpected changes.
  • Verify site forms and Elementor content still work after updating.
  • Track CVE and Wordfence records for exploitation or fix updates.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2024-0516 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2024-0516Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wproyalRoyal Addons for Elementor – Addons and Templates Kit for Elementor0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.