CVE-2025-8592

Inspiro <= 2.1.2 - Cross-Site Request Forgery to Arbitrary Plugin Installation

2025-08-20 16:43
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.1.3
Affected Theme
Inspiro
Affected Version
<= 2.1.2
CVSS
8.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-8592
View all Inspiro vulnerabilities

At a glance

CVE-2025-8592 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Inspiro WordPress theme, affecting versions <= 2.1.2. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.1.3; sites on affected versions should update now. Disclosed August 2025, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Inspiro theme for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.2. This is due to missing or incorrect nonce validation on the inspiro_install_plugin() function. This makes it possible for unauthenticated attackers to install plugins from the repository via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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. A successful exploit has high impact on integrity, availability.

CWE-352: Cross-Site Request Forgery (CSRF)

Inspiro <= 2.1.2 carries this weakness at inspiro_install_plugin(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Inspiro the fix is 2.1.3: builds <= 2.1.2 are affected, anything from 2.1.3 onward is not.

Remediation

Update to version 2.1.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Inspiro: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Inspiro 2.1.3 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Alerts

External References

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