dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2025-1441

HIGH · 8.8 CVSS v3.1 Published 2025-02-19
Fix available
A fix is available. Upgrade to after 1.7.1007 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 and Templates plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7.1007. This is due to missing or incorrect nonce validation on the 'wpr_filter_woo_products' function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 and Templates plugin for WordPress versions up to 1.7.1007 lacks proper nonce validation on the wpr_filter_woo_products function, allowing unauthenticated attackers to forge requests that can inject malicious web scripts through social engineering of site administrators.

MitigationUpdate the plugin to version 1.7.1008 or later, which includes proper nonce validation for the affected function.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Royal Elementor AddonsWordPress extension
Affected:<= 1.7.1007

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Royal Elementor Addons plugin is installed
    Navigate to WordPress admin Dashboard > Plugins and locate 'Royal Elementor Addons' in the list of installed plugins, or check for the plugin directory at wp-content/plugins/royal-elementor-addon/ via file system
    Affected if The plugin is not installed or not present in the WordPress environment
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Royal Elementor Addons and read the version number displayed under the plugin name, or open the main plugin PHP file (e.g., wppb-start.php or similar in the plugin root) and locate the 'Version:' header comment
    Affected if The version displayed is 1.7.1007 or any version number lower than 1.7.1008
  3. Verify the vulnerable function exists
    Access the WordPress file system and search for the function name 'wpr_filter_woo_products' in PHP files within the plugin directory (typically /wp-content/plugins/royal-elementor-addon/). Use grep or a file search to locate this function definition
    Affected if The function wpr_filter_woo_products is found in the plugin files, indicating the vulnerable code path exists
  4. Check for nonce validation on the affected function
    Examine the wpr_filter_woo_products function code directly. Look for wp_verify_nonce, check_admin_referer, or wp_nonce_field calls within or immediately before this function executes its action handler
    Affected if The function executes without any nonce verification check, allowing unauthenticated requests to trigger the action

If Royal Elementor Addons version 1.7.1007 or earlier is installed and the wpr_filter_woo_products function lacks nonce validation checks, the environment is affected by CVE-2025-1441 and vulnerable to injected malicious script execution via forged requests.

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
Upgrade available Upgrade to a release after 1.7.1007
Interim mitigation

Update the plugin to version 1.7.1008 or later, which includes proper nonce validation for the affected function.

Recommended fix Moderate confidence

Latest version of Royal Elementor Addons and Templates (version > 1.7.1007)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Royal Elementor Addons and Templates' in the plugin list
  4. Check if an update is available and install the latest version
  5. Alternatively, navigate to Dashboard > Updates and ensure the plugin is updated
  6. After updating, verify the site still functions correctly

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

Fix this in Royal Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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