Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as Contributor user
-
DeliveryInject JavaScript into gallery setting
-
ExploitPayload stored unescaped in HTML attribute
-
ExecutionAdministrator views page with gallery
-
ImpactScript executes in admin browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution 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 Contributor-level role or higher on a site running Gallery PhotoBlocks before 1.3.6, and the ability to edit the affected gallery setting whose value is output unescaped into an HTML attribute. Exploitation is NOT self-triggering: a victim (typically an administrator or other user) must view a page containing the malicious gallery (UI:R) for the stored payload to execute. Limiting factors that reduce real-world risk: it is not unauthenticated (an attacker needs at least Contributor access, so sites that do not grant untrusted users posting roles are largely unaffected), it depends on victim interaction (viewing the gallery page), and it is fixed in 1.3.6. |
| Impact | This is a stored (persistent) Cross-Site Scripting flaw (CWE-79) with a vendor/NVD CVSS 3.1 base score of 6.8 (MEDIUM). The input vector (AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H) is internally inconsistent with the description and should be treated with caution: it specifies PR:H (high privilege) and S:U with full C:H/I:H/A:H impact, yet the description explicitly states exploitation requires only Contributor-level access - a LOW-privilege authenticated WordPress role - and the impact of a stored XSS is confidentiality/integrity of the victim's browser session, not unscoped full-system compromise. This points to PR:L (not PR:H) and a scope change (S:C) with limited C/I impact, which is why my independent assessment lands lower than 6.8. No EPSS score, CISA KEV listing, or public POC was provided in the intelligence, so exploitation status is 'no public exploit identified at time of analysis' - there is no evidence of active or automated exploitation. Realistically this is a medium-priority, context-dependent issue rather than an emergency: it matters on multi-author WordPress sites that grant Contributor accounts to semi-trusted users, where a low-privilege author can escalate impact by landing script in an administrator's browser. Single-author or tightly-controlled sites face little practical risk. A patch is available (1.3.6), which makes remediation straightforward. |
| Exploit ScenarioDerived | A multi-author WordPress site grants a semi-trusted user a Contributor account. That user edits a Gallery PhotoBlocks gallery setting, injecting a malicious JavaScript payload that is stored unescaped in an HTML attribute. When an administrator later views any page rendering that gallery, the script executes in their authenticated session, enabling session/cookie theft or admin-level actions. No public exploit code was identified, but the technique is standard stored-XSS and trivial to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Stored cross-site scripting in the Gallery PhotoBlocks WordPress plugin before 1.3.6 allows authenticated users with Contributor-level access or higher to save JavaScript into one of the plugin's gallery settings, which is then written into an HTML attribute without sanitization or escaping, so the payload executes in the browser of any user - including an administrator - who views a page containing the gallery. Exploitation is not self-triggering: an attacker needs at least a Contributor account plus a victim who loads the affected page (UI:R), and sites that do not grant untrusted users posting roles are largely unaffected. No public exploit code has been identified at time of analysis and no EPSS score was supplied in the available intelligence; the vendor has released a fix, and our independent reassessment rates the issue MEDIUM (CVSS 3.1 base reflecting PR:L, S:C, C:L/I:L/A:N), which is lower in privilege prerequisite but broader in scope than NVD's published 6.8 vector.
RemediationAI
Upgrade Gallery PhotoBlocks to 1.3.6 or later - this is the vendor-released patch and the only complete fix, and it should be applied via the WordPress plugin updater or by downloading the release from the vendor; confirm the update completed and purge any page cache, since the stored payload already in the database will continue to render until the vulnerable output path is gone. Because the injection is persistent, patching alone does not remove previously stored malicious values: audit and delete suspicious gallery settings / post meta created by Contributor accounts after the update. If immediate patching is not possible, the most effective compensating control is to revoke Contributor and higher posting privileges from untrusted users, which removes the PR:L prerequisite entirely - but this breaks multi-author workflows and membership-site content submission, so it is a temporary measure. Disabling (deactivating or, better, uninstalling) the plugin eliminates the vulnerable output path at the cost of losing the gallery functionality. Adding a Content-Security-Policy that forbids inline script and restricts script-src to trusted origins will blunt execution of the injected handler, but it can break other plugins and themes that rely on inline scripts and requires careful testing. Deploying a WAF rule that blocks markup-bearing characters in gallery-setting submissions provides defense in depth but is bypassable and should not be treated as a substitute for patching. No public exploit code has been identified at time of analysis, which lowers the urgency of emergency mitigations but does not change the need to reach 1.3.6 promptly.
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
The vulnerable component is a WordPress gallery plugin that stores per-gallery configuration as serialized settings (post meta or plugin options) and renders those values on the front end. This is a CWE-79 (Improper Neutralization of Input During Web Page Generation) flaw of the stored/persistent XSS subclass and, more specifically, an HTML-attribute-context injection: one gallery setting is echoed directly into an HTML attribute without encoding, so an attacker-controlled value containing quote characters and event handlers survives storage and breaks out of the attribute when the gallery markup is generated. Because the sink is an attribute rather than a text node, standard text-escaping habits do not protect it - the correct fix is context-aware attribute encoding (esc_attr()) or JSON encoding if the value is consumed by JavaScript. WordPress's role model is central to the risk: Contributors can create but not publish posts, yet the malicious value is persisted server-side and executes when any user, including an Administrator, renders the gallery page. Note the vector discrepancy between sources: NVD publishes CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H (6.8), implying a higher-privileged attacker and no scope change, whereas our authoritative independent reassessment uses CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N - reflecting that Contributor-level (PR:L) accounts suffice, that the script crosses a privilege boundary from a low-privileged author into an administrator's session (S:C), and that the practical impact on confidentiality and integrity is limited (C:L/I:L). The EUVD record (EUVD-2026-96128) tracks the same affected range, Gallery PhotoBlocks 1.3.5 and earlier, with 1.3.6 as the fixed boundary.
Know when WordPress 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:H/UI:R/S:U/C:H/I:H/A:H
Contributor role maps to PR:L (not PR:H); victim must view the gallery page so UI:R; stored script executes in another user's browser so S:C with limited C:L/I:L and no availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Gallery PhotoBlocks WordPress plugin before 1.3.6 does not sanitize and escape one of its gallery settings before outputting it into an HTML attribute, allowing users with Contributor-level access and above to store JavaScript that executes in the browser of anyone who views a page containing the gallery, including administrators.
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
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-96128
GHSA-pccf-qp9v-4p26
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB