CVE-2026-119611 json
Photo Gallery, Sliders, Proofing and Themes <= 4.5.5 - Unauthenticated Stored Cross-Site Scripting via 'ajax_pagination_referrer' Parameter on /ngg_tag/<tag>/
published yesterday modified yesterday also EUVD-2026-131411
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-119611 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- smub Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/eb17bfea-9648-4395-b69e-b159f3bdfef5?source=cve
- plugins.trac.wordpress.org /browser/nextgen-gallery/tags/4.5.5/src/DisplayTypes/Thumbnails.php#L128
- plugins.trac.wordpress.org /browser/nextgen-gallery/tags/4.5.5/src/DisplayType/Controller.php#L811
- plugins.trac.wordpress.org /browser/nextgen-gallery/tags/4.5.5/src/DisplayedGallery/Renderer.php#L460
- plugins.trac.wordpress.org /browser/nextgen-gallery/tags/4.5.5/src/DisplayTypes/Taxonomy.php#L96
- plugins.trac.wordpress.org /browser/nextgen-gallery/tags/4.5.5/src/Util/RoutingApp.php#L627
- plugins.trac.wordpress.org /browser/nextgen-gallery/tags/4.5.5/static/Thumbnails/ajax_pagination.js#L21
- plugins.trac.wordpress.org /changeset?reponame=&new=3793265%40nextgen-gallery&old=3773861%40nextgen-gallery
- plugins.trac.wordpress.org /changeset/3793263/nextgen-gallery/trunk/src/DisplayTypes/Thumbnails.php
Sources
- CVE List CVE-2026-119611
- NVD CVE-2026-119611
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.