WordPress security changelog
MEDIUM CVE-2026-107757 Deferred

Gallery Custom Links: Cross-site scripting

A Subscriber can combine crafted comment HTML with a specially constructed display_name to exploit Gallery Custom Links. Its default-enabled full-page buffer uses simple_html_dom substitutions after WordPress has applied kses and attribute escaping, turning previously processed output into stored cross-site scripting. The attack depends on the coordinated comment and name inputs, not merely changing a profile name. Published affected versions: <= 2.3.3.

CVE / CNA score 4.9 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Gallery Custom Links
Plugin slug
gallery-custom-links
Affected
<= 2.3.3
Safe version
2.3.4
Published
Oct 14, 2026
Weakness
CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

This CVE was published Oct 14, 2026 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Gallery Custom Links to 2.3.4 or later in the same release line. The official author changelog identifies a matching fix. Official release notes: https://wordpress.org/plugins/gallery-custom-links/#developers.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Gallery Custom Links plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name (profile.php) + comment (wp-comments-post.php)' parameter in all versions up to, and including, 2.3.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit requires two coordinated inputs from the same authenticated attacker: an HTML comment payload stored in a comment body (preserved verbatim by WordPress comment kses) and a matching simple_html_dom noise key placed in the attacker's display_name (which survives esc_attr() intact), with substitution occurring after both filters have run during the plugin's default-on output-buffering pass over the full rendered page.

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

References

Primary and upstream sources