UiCore Elements <= 1.3.0 - Missing Authorization to Unauthenticated Arbitrary File Read
Strategic Overview
- Status
- Patched in 1.3.1
- Affected Plugin
- UiCore Elements – Free widgets and templates for Elementor
- Affected Version
<= 1.3.0- CVSS
- 7.5High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-6253
At a glance
CVE-2025-6253 is a high-severity Missing Authorization vulnerability in the UiCore Elements WordPress plugin, affecting versions <= 1.3.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.3.1; sites on affected versions should update now. Disclosed August 2025, reported by mikemyers.
Vulnerability Overview
The UiCore Elements – Free Elementor widgets and templates plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 1.3.0 via the prepare_template() function due to a missing capability check and insufficient controls on the filename specified. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-862: Missing Authorization
UiCore Elements <= 1.3.0 carries this weakness at prepare_template(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For UiCore Elements the fix is 1.3.1: builds <= 1.3.0 are affected, anything from 1.3.1 onward is not.
Remediation
Update to version 1.3.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: UiCore Elements 1.3.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in UiCore Elements – Free widgets and templates for Elementor
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C