CVE-2025-15524

Gallery by FooGallery <= 3.1.9 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Gallery Metadata Exposure

2026-02-10 12:28
s00me00ne

Strategic Overview

Status
Patched in 3.1.10
Affected Plugin
Gallery : FooGallery
Affected Version
<= 3.1.9
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-15524
View all Gallery : FooGallery vulnerabilities

At a glance

CVE-2025-15524 is a medium-severity Missing Authorization vulnerability in the Gallery WordPress plugin, affecting versions <= 3.1.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.1.10; sites on affected versions should update now. Disclosed February 2026, reported by s00me00ne.

Vulnerability Overview

The Gallery by FooGallery plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the ajax_get_gallery_info() function in all versions up to, and including, 3.1.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve metadata (name, image count, thumbnail URL) of private, draft, and password-protected galleries by enumerating gallery IDs.

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-862: Missing Authorization

Gallery <= 3.1.9 carries this weakness at ajax_get_gallery_info(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Gallery the fix is 3.1.10: builds <= 3.1.9 are affected, anything from 3.1.10 onward is not.

Remediation

Update to version 3.1.10, 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 3.1.10 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-15524https://www.wordfence.com/threat-intel/vulnerabilities/id/10735038-69dd-4b74-9374-38379832cdcbhttps://nvd.nist.gov/vuln/detail/CVE-2025-15524

Related records

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