CVE-2025-39443

Verge3D <= 4.9.0 - Cross-Site Request Forgery

2025-04-17 00:00
Nabil Irawan

Strategic Overview

Status
Patched in 4.9.3
Affected Plugin
Verge3D Publishing and E-Commerce
Affected Version
<= 4.9.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-39443
View all Verge3D Publishing and E-Commerce vulnerabilities

At a glance

CVE-2025-39443 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Verge3D Publishing and E-Commerce WordPress plugin, affecting versions <= 4.9.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.9.3; sites on affected versions should update now. Disclosed April 2025, reported by Nabil Irawan.

Vulnerability Overview

The Verge3D Publishing and E-Commerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.9.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 Verge3D Publishing and E-Commerce <= 4.9.0 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 Verge3D Publishing and E-Commerce the fix is 4.9.3: builds <= 4.9.0 are affected, anything from 4.9.3 onward is not.

Remediation

Update to version 4.9.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-39443https://www.wordfence.com/threat-intel/vulnerabilities/id/0dbce573-fced-4c0f-ba1e-2932c166545chttps://nvd.nist.gov/vuln/detail/CVE-2025-39443

Related records

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