Skip to main content
Menu
CVEs

CVE

Sarah Giles Dynamic User Directory reflected XSS in WordPress plugin

Affects the Dynamic User Directory WordPress plugin, version 2.4 and earlier. CVSS rates it 7.1 (high), and the checked facts name no fixed version.

CVE-2026-125856EUVD-2026-125412GHSA-5VVR-RMG2-XGX7

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

7.1HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Dynamic User Directory WordPress plugin version 2.4 or earlier

Published
Last modified
Reference
Last checked
0.23% · 13th percentile
24/100
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Sarah Giles Dynamic User Directory dynamic-user-directory allows Reflected XSS.This issue affects Dynamic User Directory: from n/a through 2.4.

Who should check

Sites running the Dynamic User Directory WordPress plugin version 2.4 or earlier

“WordPress Dynamic User Directory Plugin <= 2.4 is vulnerable”

patchstack.com

cve.now Index

24cve.now Index 24 of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    Dynamic User Directory WordPress plugin version 2.4 or earlier
  • Workaround: The checked facts do not describe a workaround. Until a fix is confirmed, the checked facts offer no specific steps to limit the risk.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125856 (WordPress Dynamic User Directory plugin <= 2.4 - Cross Site Scripting (XSS) vulnerability), 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-125856 (entry last updated 2026-11-13):
Affected:
- Sarah Giles Dynamic User Directory: through 2.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Dynamic User Directory WordPress plugin version 2.4 or earlier (source: https://patchstack.com/database/wordpress/plugin/dynamic-user-directory/vulnerability/wordpress-dynamic-user-directory-plugin-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-125856 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125856 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://patchstack.com/database/wordpress/plugin/dynamic-user-directory/vulnerability/wordpress-dynamic-user-directory-plugin-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve
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-125856
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-125856"}.

Public exploit activity

100%0Nov 13Nov 17
  • EPSS: 0.23%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • dynamic-user-directory

    through 2.4

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125856

Is CVE-2026-125856 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: cve.now feed data

What does this mean?

This is a Cross Site Scripting (XSS) flaw. Attackers can inject malicious scripts into the site that steal visitor data or hijack visitor accounts.Source: patchstack.com

Which versions are affected by CVE-2026-125856?

dynamic-user-directory: through 2.4.Source: cve.now feed data

Am I affected, and how do I check?

The checked facts cover Dynamic User Directory, a WordPress plugin by Sarah Giles, at version 2.4 or earlier. To check a installed copy, look at the plugin version shown on the WordPress Plugins screen.Source: patchstack.com

How do I fix CVE-2026-125856?

The checked facts do not name a fixed version or vendor patch. Check the vendor's advisory for a fixed release before relying on any update.Source: patchstack.com

What if there's no patch?

The checked facts do not describe a workaround. Until a fix is confirmed, the checked facts offer no specific steps to limit the risk.Source: patchstack.com