Worthy – VG WORT Integration für WordPress <= 1.6.5-6497609 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.7.0-0cde1c2
- Affected Plugin
- Worthy – VG WORT Integration für WordPress
- Affected Version
<= 1.6.5-6497609- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-24417
At a glance
CVE-2023-24417 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Worthy WordPress plugin, affecting versions <= 1.6.5-6497609. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7.0-0cde1c2; sites on affected versions should update now. Disclosed May 2023, reported by yuyudhn.
Vulnerability Overview
The Worthy – VG WORT Integration für WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.6.5-6497609. This is due to missing nonce validation on various functions called via admin_post hooks. This makes it possible for unauthenticated attackers to control many of the plugins 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)
Reaching this weakness in Worthy <= 1.6.5-6497609 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 Worthy the fix is 1.7.0-0cde1c2: builds <= 1.6.5-6497609 are affected, anything from 1.7.0-0cde1c2 onward is not.
Remediation
Update to version 1.7.0-0cde1c2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Worthy: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Worthy 1.7.0-0cde1c2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C