# CVE-2025-11363: Royal Elementor Addons and Templates < 1.7.1037 - Unauthenticated Media File Upload

> Unauthenticated attackers can upload arbitrary media files via the wpr_addons_upload_file action, potentially leading to code execution or data modification.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** GHSA-f6cr-5vcg-p3cg

## What is CVE-2025-11363?

CVE-2025-11363 is a medium-severity vulnerability in Unknown Royal Addons for Elementor, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Royal Addons for Elementor  WordPress plugin before 1.7.1037 does not have proper authorisation, allowing unauthenticated users to upload media files via the wpr_addons_upload_file action.

## Which versions are affected by CVE-2025-11363?


## How do I fix CVE-2025-11363?

No fix has been published for CVE-2025-11363 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11363 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11363 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11363 and fix it if it is affected.

What it is: CVE-2025-11363 is a medium-severity vulnerability in Unknown Royal Addons for Elementor, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11363 exists.

Affected product: Unknown Royal Addons for Elementor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11363/ (Markdown: https://insights.sbomify.com/CVE-2025-11363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11363
- OSV: https://osv.dev/vulnerability/CVE-2025-11363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11363/
Summaries are generated and may contain mistakes; the official description above is the record.