CVE-2025-32623

PlainInventory <= 3.1.9 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2025-04-09 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 4.0.0
Affected Version
<= 3.1.9
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-32623
View all Zintory – Inventory Manager vulnerabilities

At a glance

CVE-2025-32623 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Zintory WordPress plugin, affecting versions <= 3.1.9. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.0; sites on affected versions should update now. Disclosed April 2025, reported by Abdi Pranata.

Vulnerability Overview

The PlainInventory – Inventory Management Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.9. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts 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.

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

Reaching this weakness in Zintory <= 3.1.9 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 Zintory the fix is 4.0.0: builds <= 3.1.9 are affected, anything from 4.0.0 onward is not.

Remediation

Update to version 4.0.0, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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