CVE-2025-8592 json
Inspiro <= 2.1.2 - Cross-Site Request Forgery to Arbitrary Plugin Installation
published last yr. modified 4mo ago also EUVD-2025-25454
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-8592 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H |
Affected products
- wpzoom Inspiro
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/20f461d1-aeb2-4913-804c-6a081e48765a?source=cve
- themes.trac.wordpress.org /browser/inspiro/2.1.1/inc/admin/pluginInstaller/class-inspiro-plugin-installer.php#L67
- research.cleantalk.org /cve-2025-8592/
- themes.trac.wordpress.org /ticket/228813
- themes.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&new=284043%40inspiro%2F2.1.3&old=282419%40inspiro%2F2.1.2
Sources
- CVE List CVE-2025-8592
- NVD CVE-2025-8592
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.