dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4803

HIGH · 7.2 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Royal Elementor Addons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'status' parameter in the wpr_update_form_action_meta AJAX action in all versions up to, and including, 1.7.1056. This is due to insufficient input sanitization and output escaping, combined with a publicly leaked nonce that allows unauthenticated access to the AJAX handler. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

Stored XSS vulnerability in Royal Elementor Addons WordPress plugin. The wpr_update_form_action_meta AJAX handler fails to sanitize the 'status' parameter during input and fails to escape it during output. Combined with a publicly leaked nonce that enables unauthenticated access, attackers can inject arbitrary JavaScript that executes when users view infected pages.

MitigationUpdate Royal Elementor Addons plugin to version newer than 1.7.1056. If immediate update is not feasible, disable the plugin until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Royal Elementor Addons plugin is installed
    Check the WordPress plugins directory at /wp-content/plugins/royal-elementor-addons/ or view the installed plugins list in wp-admin under Plugins
    Affected if The plugin directory or plugin list shows Royal Elementor Addons as active or installed
  2. Identify the installed plugin version
    Open the main plugin file (royal-elementor-addons.php) or readme.txt in the plugin directory and locate the Version header
    Affected if The version number is 1.7.1056 or lower (any version up to and including 1.7.1056 is affected)
  3. Locate the vulnerable AJAX handler
    Search for the file containing wpr_update_form_action_meta function, typically in includes/ folder; verify the function accepts a 'status' parameter without sanitization
    Affected if The AJAX handler file exists and processes the 'status' parameter without sanitization routines
  4. Check for injected status values in the database
    Query the WordPress postmeta table for records with meta_key containing 'form_action_meta' or similar; examine the meta_value for suspicious status values containing script tags or JavaScript event handlers
    Affected if Database records contain unsanitized status values with script tags, javascript:, or event handler attributes like onmouseover/onload

A user is affected if Royal Elementor Addons plugin version 1.7.1056 or lower is installed and the wpr_update_form_action_meta AJAX handler is accessible with unsanitized 'status' values present in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Royal Elementor Addons plugin to version newer than 1.7.1056. If immediate update is not feasible, disable the plugin until the patch can be applied.

Recommended fix Moderate confidence

Royal Elementor Addons version 1.7.1057 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Royal Elementor Addons plugin
  4. 4. Check the current installed version
  5. 5. If version is 1.7.1056 or lower, update the plugin to the latest available version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4803 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4803 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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