dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-6229

HIGH · 7.2 CVSS v3.1 Published 2026-05-02
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 Server-Side Request Forgery in versions up to, and including, 1.7.1057. This is due to insufficient validation of user-supplied URLs in the render_csv_data() function, which can be bypassed by including 'docs.google.com/spreadsheets' in a query parameter, and the subsequent use of these URLs in fopen() calls without blocking internal or private network addresses. This makes it possible for authenticated attackers, with Contributor-level access and above, to make requests to arbitrary URLs and retrieve sensitive 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 confidence

The Royal Elementor Addons WordPress plugin has an SSRF vulnerability in the render_csv_data() function. Attackers with Contributor-level access can supply malicious URLs (bypassing validation via docs.google.com/spreadsheets) that are then used in fopen() calls without blocking internal/private network addresses, enabling access to sensitive internal services.

MitigationUpdate Royal Elementor Addons to version 1.7.1058 or later. Consider restricting contributor-level permissions and implementing WAF rules to block internal network requests.

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. Verify Royal Elementor Addons is installed
    Navigate to WordPress admin > Plugins and locate Royal Elementor Addons in the installed plugins list
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In Plugins list, click on the plugin to view details, or check the plugin header in wp-content/plugins/royal-elementor-addons/royal-elementor-addons.php for the Version field
    Affected if The version is earlier than 1.7.1058 (or version cannot be determined and the plugin is present)
  3. Confirm Contributor user role exists
    Go to WordPress admin > Users and review the list of users to see if any accounts have the Contributor role assigned
    Affected if At least one user with Contributor role exists on the site
  4. Inspect CSV import functionality exposure
    Check if the plugin CSV import feature is accessible by reviewing the WordPress REST API endpoints or the plugin settings for any CSV data import/render functionality
    Affected if CSV import or render_csv_data() functionality is enabled or accessible in the plugin settings
  5. Test for internal network access via the vulnerability
    If you have a staging environment, log in as a Contributor user and attempt to use the CSV import feature with a URL like http://localhost or http://127.0.0.1 to see if internal requests are blocked
    Affected if The plugin allows the CSV import feature to make requests to internal/private network addresses without proper filtering

A site is affected if Royal Elementor Addons plugin is installed with a version earlier than 1.7.1058, the CSV import feature is accessible, and users with Contributor-level access exist on the site.

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 to version 1.7.1058 or later. Consider restricting contributor-level permissions and implementing WAF rules to block internal network requests.

Recommended fix Moderate confidence

Royal Elementor Addons version > 1.7.1057 (latest available version)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Royal Elementor Addons plugin
  4. Check if the current version is 1.7.1057 or earlier
  5. If vulnerable, click Update Now to upgrade to the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number has changed to confirm the patch was applied

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6229 — 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-6229 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