CVE-2026-107757 tigroumeow CVE debrief

Who should care

Defenders responsible for WordPress installations with the Gallery Custom Links plugin should assess exposure, particularly for subscriber-level users and above, and prioritize verifying the presence of this vulnerability in their environments. They must also consider upgrading to a patched version of the plugin and review compensating controls for exposed systems.

Why it matters

The Gallery Custom Links plugin for WordPress is vulnerable to Stored Cross-Site Scripting, allowing authenticated attackers to inject arbitrary web scripts.

• Authenticated attackers with subscriber-level access and above can inject arbitrary web scripts
• Injected scripts execute whenever a user accesses an injected page
• Defenders must verify the presence of this vulnerability in their WordPress installations
• Remediation priority follows from verifying exposure and upgrading to a patched version

Technical summary

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 allows 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, impacting defenders who must verify exposure and prioritize remediation.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and assess exposure, particularly for subscriber-level users and above.

Recommended defensive actions

• Verify the presence of this vulnerability in your WordPress installations
• Assess exposure, particularly for subscriber-level users and above
• Consider upgrading to a patched version of the plugin
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should verify the presence of this vulnerability in their WordPress installations and assess exposure, particularly for subscriber-level users and above, with explicit evidence-limit language and defensive verification tasks. The exploit requires two coordinated inputs from the same authenticated attacker: an HTML comment payload stored in a comment body and a matching simple_html_dom noise key.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.