CVE-2023-44233

FooGallery <= 2.2.44 - Cross-Site Request Forgery

2023-09-29 00:00
R3N0

Strategic Overview

Status
Patched in 2.3.2
Affected Plugin
Gallery : FooGallery
Affected Version
<= 2.2.44
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-44233
View all Gallery : FooGallery vulnerabilities

At a glance

CVE-2023-44233 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Gallery WordPress plugin, affecting versions <= 2.2.44. 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.3.2; sites on affected versions should update now. Disclosed September 2023, reported by R3N0.

Vulnerability Overview

The FooGallery plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.2.44. This is due to missing nonce validation on the handle_extension_action() function. This makes it possible for unauthenticated attackers to activate, download, and deactivate extensions 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)

Gallery <= 2.2.44 carries this weakness at handle_extension_action(), 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 Gallery the fix is 2.3.2: builds <= 2.2.44 are affected, anything from 2.3.2 onward is not.

Remediation

Update to version 2.3.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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