CVE-2025-47486

Gutenberg & Elementor Templates Importer For Responsive <= 3.1.9 - Missing Authorization

2025-05-07 00:00
Marek Mikita

Strategic Overview

Status
Patched in 3.2.0
Affected Plugin
Responsive Starter Templates – Elementor Templates & Starter Sites
Affected Version
<= 3.1.9
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-47486
View all Responsive Starter Templates – Elementor Templates & Starter Sites vulnerabilities

At a glance

CVE-2025-47486 is a medium-severity Missing Authorization vulnerability in the Responsive Starter Templates WordPress plugin, affecting versions <= 3.1.9. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.0; sites on affected versions should update now. Disclosed May 2025, reported by Marek Mikita.

Vulnerability Overview

The Gutenberg & Elementor Templates Importer For Responsive plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the create_items function in versions up to, and including, 3.1.9. This makes it possible for unauthenticated attackers to create items through the REST endpoint.

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.

CWE-862: Missing Authorization

Reaching this weakness in Responsive Starter Templates <= 3.1.9 takes a caller who can reach the endpoint. 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 Responsive Starter Templates the fix is 3.2.0: builds <= 3.1.9 are affected, anything from 3.2.0 onward is not.

Remediation

Update to version 3.2.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Responsive Starter Templates 3.2.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-47486https://www.wordfence.com/threat-intel/vulnerabilities/id/7299e46f-6cff-4ecc-8c2b-100c26907c91https://nvd.nist.gov/vuln/detail/CVE-2025-47486

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C