Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as author-level WordPress user
-
ExploitCall plugin REST endpoint lacking authorization check
-
ExecutionBypass missing capability verification
-
ImpactEnumerate and read private/draft post metadata
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with author-level privileges or above on a site running Meow Gallery 5.5.4 or earlier; it works against default configurations (no special feature toggle or non-default setting is called out in the sources). Limiting factors: the PR:L requirement means an anonymous or subscriber-level user cannot exploit it, so the attacker must already possess or compromise an author+ account; no user interaction is needed (UI:N); and the impact is confined to reading metadata (ID, title, date, author, status) of private and draft posts rather than their full content or any write/modification capability. |
| Impact | This is a medium-severity authorization flaw (CVSS 6.5 per Wordfence) whose real-world urgency is moderate rather than critical. The vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N is network-reachable and low-complexity, but PR:L means exploitation requires an authenticated account with author-level privileges or above - a meaningful trust barrier that excludes anonymous internet attackers and limits the realistic attacker population to existing site users (e.g., contributors/authors on multi-author blogs or any account that has been provisioned or compromised at that level). The vuln.today decision label is 'this_month', not act_now or emergency, consistent with a plan-and-patch posture. No CISA KEV listing is present and no EPSS probability was supplied, so there is no signal of active or widespread exploitation; exploitation status is best described as no public working exploit identified. One signal to weigh carefully: the input rates confidentiality as C:H, but the disclosed data is metadata only (post ID, title, date, author, status) of private/draft posts - not full post content - which I assess as a Low rather than High confidentiality impact; verify the intended scope with Wordfence if the distinction matters to prioritization. Net: a genuine but bounded information-disclosure issue, appropriate for routine patching within the month rather than emergency response. |
| Exploit ScenarioDerived | An attacker who already holds an author-level (or higher) account on the WordPress site - for example a contributor on a multi-author blog, or an account obtained through credential compromise - sends requests to the Meow Gallery plugin's REST endpoints, which fail to verify that the caller is authorized for the action. This lets them enumerate and read metadata (post ID, title, date, author, status) of all private and draft posts site-wide, including drafts authored by other users. No confirmed public working exploit code was identified; the available references point to the plugin source and the patch changeset rather than to a published PoC. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Authorization bypass in the Meow Gallery plugin for WordPress, in all versions up to and including 5.5.4, lets any authenticated user holding author-level access or higher enumerate and read metadata - post ID, title, date, author and status - for every private and draft post on the site, including unpublished content belonging to other users. The root cause is a missing capability check on the plugin's REST handlers and core class (CWE-862), reachable remotely with PR:L and no user interaction against default configurations. Wordfence rates the issue 6.5, while our assessment narrows the confidentiality impact to metadata disclosure rather than post body content; no public exploit code has been identified at time of analysis, and the vulnerability is not in CISA KEV.
RemediationAI
Upgrade the Meow Gallery plugin to version 5.5.5, which is the release immediately following the vulnerable 5.5.4 tag and the version in which the authorization check was added - the diff is published at plugins.trac.wordpress.org/changeset?old_path=/meow-gallery/tags/5.5.4&new_path=/meow-gallery/tags/5.5.5, and the advisory is at wordfence.com/threat-intel/vulnerabilities/id/1f35d2c6-b631-40ba-b92a-972a891d4623. Because the defect is a missing capability check inside the plugin's REST handlers, the supplied sources describe no feature toggle, nonce setting, or configuration switch that closes the hole, so updating is the complete fix and there is no vendor-documented workaround to substitute for it. Where an immediate update is not possible, the effective compensating control is to reduce the population of accounts that satisfy the PR:L prerequisite: audit and remove author-level and higher accounts that do not need them, temporarily demote or suspend unused author accounts, and restrict registration and role-escalation paths - the trade-off is editorial disruption for legitimate authors. Site-level REST API restriction (for example blocking /wp-json/meow-gallery/* at the WAF or web server) would cut the exposed routes, but it will also break the plugin's gallery features in the editor and front end, so it should be treated as a short-term stopgap until 5.5.5 is deployed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Meow Gallery is a WordPress gallery plugin whose front-end and editor features are backed by custom REST routes and a core bootstrap class; the reported weak points are classes/rest.php (around lines 123 and 622) and classes/core.php (line 77) in the 5.5.1 tag, which is representative of the pre-fix code base. CWE-862 (Missing Authorization) describes the class precisely: the handlers perform an action - returning post metadata for private and draft posts - without verifying that the calling user has the capability required for those specific posts, so the check that WordPress normally enforces through current_user_can() and post-level capability mapping is absent. Because the routes are exposed through the WordPress REST API over the network and the plugin's own capability expectation is never applied, any logged-in account at author level or above satisfies the code path, and the query returns metadata across the whole site rather than only the caller's own posts. The exposed fields are structural metadata (ID, title, date, author, status), not rendered post content, which is why our assessment records confidentiality as limited (C:L) even though the vendor's vector claims high confidentiality. Nothing in the supplied sources describes a race condition, memory-safety issue, or special configuration toggle; exploitation is a plain authorization gap in the REST layer.
Know when Meow Gallery gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Author-level account required (PR:L), network and low-complexity (AV:N/AC:L); only post metadata is exposed so C:L, with no integrity or availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorNVD
DescriptionNVD
The Meow Gallery plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.5.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with author-level access and above, to enumerate and read metadata - including post ID, title, date, author, and status - of all private and draft posts on the site, including those authored by other users.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Meow Gallery
View allThe Meow Gallery WordPress plugin before 4.1.9 does not sanitise, validate or escape the ids attribute of its gallery sh
Unauthenticated attackers can invoke arbitrary registered shortcodes on WordPress sites running the Meow Gallery plugin
Stored cross-site scripting in Meow Gallery WordPress plugin (all versions before 5.5.2) allows any WordPress user holdi
Blind SQL injection in Meow Gallery up to version 5.4.4 allows high-privileged attackers to extract sensitive data from
Information disclosure in the Meow Gallery WordPress plugin before 5.5.5 lets authenticated users holding Author-level a
Stored cross-site scripting in the Meow Gallery WordPress plugin (all versions up to and including 5.5.1) lets an authen
Meow Gallery plugin for WordPress (all versions through 5.4.4) exposes an unprotected REST API endpoint that permits any
EUVD-2026-114259
GHSA-jxc5-78m4-q5w9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB