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.
Published: 2026-10-14
Score: 4.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Stored Cross‑Site Scripting through comment author display name and comment body
Action: Patch immediately
AI Analysis

Impact

The Gallery Custom Links plugin allows a Subscriber or higher level user to inject arbitrary JavaScript into pages by combining an unescaped display name with a comment body that preserves HTML. The attacker’s payload is stored and later injected into the rendered page, enabling arbitrary script execution in the context of users who view the affected content. This vulnerability is a classic Cross‑Site Scripting flaw (CWE‑79).

Affected Systems

Any WordPress site running Gallery Custom Links version 2.3.3 or earlier is affected. The vulnerability is present in the tigroumeow:Gallery Custom Links installation, and the issue remains until the plugin is upgraded beyond 2.3.3.

Risk and Exploitability

The CVSS score of 4.9 signifies moderate risk. The EPSS score of less than 1 % indicates a very low likelihood of exploitation in current real‑world usage, and the issue is not listed in the CISA KEV catalog. The attack requires an authenticated account with at least subscriber privileges, creation of a comment containing the malicious HTML payload, and setting a matching noise key in the user’s display name, which survive WordPress’s default filtering before the plugin’s output‑buffering pass performs substitution. Because both inputs must be coordinated, the attack surface is limited, but once achieved it can compromise any visitor to the commented page.

Generated by OpenCVE AI on October 15, 2026 at 23:56 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gallery Custom Links to the latest released version beyond 2.3.3 where the sanitization issue is fixed.
  • If an upgrade is not immediately feasible, temporarily restrict Subscriber+ users from posting comments or enforce comment moderation that removes any JavaScript payloads from comment bodies and display names.
  • Deploy a WordPress security plugin or custom filter to automatically strip or escape script tags and HTML attributes from user display names and comment content until the plugin is updated.

Generated by OpenCVE AI on October 15, 2026 at 23:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 14 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 14 Oct 2026 08:00:00 +0000

Type Values Removed Values Added
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.
Title Gallery Custom Links <= 2.3.3 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Comment Author Display Name + Comment HTML Comment Body
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-14T14:18:40.709Z

Reserved: 2026-10-08T19:00:40.411Z

Link: CVE-2026-107757

cve-icon Vulnrichment

Updated: 2026-10-14T14:16:16.713Z

cve-icon NVD

Status : Deferred

Published: 2026-10-14T08:17:05.040

Modified: 2026-10-14T15:17:06.577

Link: CVE-2026-107757

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T00:00:16Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')