CVE-2023-36691

WebwinkelKeur <= 3.24 - Cross-Site Request Forgery

2023-06-30 00:00
qilin_99

Strategic Overview

Status
Patched in 3.25
Affected Version
< 3.25
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-36691
View all WebwinkelKeur: Webshop keurmerk & reviews for WordPress vulnerabilities

At a glance

CVE-2023-36691 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WebwinkelKeur WordPress plugin, affecting versions < 3.25. 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 3.25; sites on affected versions should update now. Disclosed June 2023, reported by qilin_99.

Vulnerability Overview

The WebwinkelKeur plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.24. This is due to missing nonce validation on the options_page() function. This makes it possible for unauthenticated attackers to modify 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)

WebwinkelKeur < 3.25 carries this weakness at options_page(), 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 WebwinkelKeur the fix is 3.25: builds < 3.25 are affected, anything from 3.25 onward is not.

Remediation

Update to version 3.25, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WebwinkelKeur: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WebwinkelKeur 3.25 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