CVE-2024-12114

FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry & Carousel <= 2.4.29 - Insecure Direct Object Reference to Authenticated (Custom+) Arbitrary Post/Page Updates

2025-03-07 16:21
Stiofan

Strategic Overview

Status
Patched in 2.4.30
Affected Plugin
Gallery : FooGallery
Affected Version
<= 2.4.29
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-12114
View all Gallery : FooGallery vulnerabilities

At a glance

CVE-2024-12114 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Gallery WordPress plugin, affecting versions <= 2.4.29. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom level or above. The issue is fixed in version 2.4.30; sites on affected versions should update now. Disclosed March 2025, reported by Stiofan.

Vulnerability Overview

The FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry & Carousel plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.4.29 via the foogallery_attachment_modal_save AJAX action due to missing validation on a user controlled key (img_id). This makes it possible for authenticated attackers, with granted access and above, to update arbitrary post and page content. This requires the Gallery Creator Role setting to be a value lower than 'Editor' for there to be any real impact.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Gallery <= 2.4.29 carries this weakness at Editor, and reaching it takes an account at Custom level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Gallery the fix is 2.4.30: builds <= 2.4.29 are affected, anything from 2.4.30 onward is not.

Remediation

Update to version 2.4.30, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Gallery 2.4.30 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-12114https://www.wordfence.com/threat-intel/vulnerabilities/id/f4fe3ad9-247f-4e5d-8c79-0970afaa7729https://nvd.nist.gov/vuln/detail/CVE-2024-12114

Related records

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