dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13067

HIGH · 8.8 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Addons for Elementor plugin for WordPress is vulnerable to arbitrary file upload in all versions up to, and including, 1.7.1049. This is due to insufficient file type validation detecting files named main.php, allowing a file with such a name to bypass sanitization. This makes it possible for authenticated attackers, with author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Addons for Elementor plugin for WordPress versions up to 1.7.1049 contains an arbitrary file upload vulnerability caused by insufficient file type validation that fails to properly sanitize files named 'main.php', allowing authenticated users with author-level access or higher to bypass upload restrictions and upload malicious PHP files leading to potential remote code execution.

MitigationUpdate Royal Addons for Elementor to version 1.7.1050 or later to apply the vendor patch. If an update is unavailable, disable the plugin immediately and review server access logs for signs of exploitation.

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

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

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 Addons for Elementor is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'royal-addons-for-elementor' or 'royal-elementor-addons', or query the WordPress database wp_options table for the active_plugins option containing 'royal-addons' or 'royal-elementor'.
    Affected if The plugin folder or database entry exists in your WordPress installation.
  2. Determine the installed plugin version
    Locate the main plugin file (usually index.php or the primary PHP file in the plugin folder) and look for the 'Version' header comment, or query the WordPress database wp_options table for the option_name containing 'royal_addons' or 'royal_elementor' version information.
    Affected if The installed version is 1.7.1049 or any earlier version (versions prior to 1.7.1050 are affected).
  3. Identify users with author-level access
    Query the WordPress database wp_users and wp_usermeta tables to identify accounts with user_level 2 or higher, or roles including Author, Editor, or Administrator. These accounts can exploit the vulnerability.
    Affected if Any user account with Author, Editor, or Administrator role exists in the WordPress users table.
  4. Inspect upload directories for suspicious PHP files
    Search WordPress upload folders (typically wp-content/uploads/ and subdirectories) for files named 'main.php' or other PHP files that appear unfamiliar or were uploaded recently. Use the command: find /path/to/wp-content/uploads -name '*.php' -mtime -30 to find recently modified PHP files.
    Affected if Any PHP files named 'main.php' or other unexpected PHP files exist in upload directories, especially if created recently.
  5. Review server access logs for upload endpoint activity
    Examine web server access logs (Apache error.log, Nginx access.log, or similar) for POST requests to WordPress admin-ajax.php or the plugin's upload handlers. Look for patterns indicating file upload attempts, especially requests containing 'main.php' in the request body or multipart form data.
    Affected if Logs show POST requests to upload functionality from authenticated users, particularly those containing PHP file uploads or requests with 'main.php' filename.

Your environment is affected if Royal Addons for Elementor is installed with version 1.7.1049 or earlier AND any user account with Author-level access or higher exists on the WordPress 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Royal Addons for Elementor to version 1.7.1050 or later to apply the vendor patch. If an update is unavailable, disable the plugin immediately and review server access logs for signs of exploitation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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