CVE-2024-31921

Ultimate Product Catalogue <= 5.2.15 - Cross-Site Request Forgery via reset_settings()

2024-04-10 00:00
Dhabaleshwar Das

Strategic Overview

Status
Patched in 5.2.16
Affected Plugin
Ultimate Product Catalog
Affected Version
<= 5.2.15
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-31921
View all Ultimate Product Catalog vulnerabilities

At a glance

CVE-2024-31921 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Ultimate Product Catalog WordPress plugin, affecting versions <= 5.2.15. 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 5.2.16; sites on affected versions should update now. Disclosed April 2024, reported by Dhabaleshwar Das.

Vulnerability Overview

The Ultimate Product Catalogue plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.2.15. This is due to missing or incorrect nonce validation on the reset_settings() function. This makes it possible for unauthenticated attackers to reset the plugin's settings 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)

Ultimate Product Catalog <= 5.2.15 carries this weakness at reset_settings(), 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 Ultimate Product Catalog the fix is 5.2.16: builds <= 5.2.15 are affected, anything from 5.2.16 onward is not.

Remediation

Update to version 5.2.16, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-31921https://www.wordfence.com/threat-intel/vulnerabilities/id/68721ded-0a80-4cff-aaf0-59b2fcf67456https://nvd.nist.gov/vuln/detail/CVE-2024-31921

Related records

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