CVE-2024-10480

3DPrint Lite <= 2.0.9.9 - Cross-Site Request Forgery to Settings Update

2024-11-15 00:00
Vuln Seeker Cybersecurity Team

Strategic Overview

Status
Patched in 2.1
Affected Plugin
3DPrint Lite
Affected Version
<= 2.0.9.9
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-10480
View all 3DPrint Lite vulnerabilities

At a glance

CVE-2024-10480 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the 3DPrint Lite WordPress plugin, affecting versions <= 2.0.9.9. 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 2.1; sites on affected versions should update now. Disclosed November 2024, reported by Vuln Seeker Cybersecurity Team.

Vulnerability Overview

The 3DPrint Lite plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.9.9. This is due to missing or incorrect nonce validation on the 'p3dlite_settings' action. This makes it possible for unauthenticated attackers to update 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)

3DPrint Lite <= 2.0.9.9 carries this weakness at p3dlite_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 3DPrint Lite the fix is 2.1: builds <= 2.0.9.9 are affected, anything from 2.1 onward is not.

Remediation

Update to version 2.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-10480https://www.wordfence.com/threat-intel/vulnerabilities/id/0c29e242-b05c-4876-8948-1278982d6fbchttps://nvd.nist.gov/vuln/detail/CVE-2024-10480

Related records

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