PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-104726 jeroenpeters1986 CVE debrief

The Name Directory plugin for WordPress has a Stored Cross-Site Scripting vulnerability via the 'dir' Shortcode Attribute in all versions up to, and including, 1.34.2. This allows authenticated attackers with contributor-level access and above to inject arbitrary web scripts in pages that will execute when a user accesses an injected page. The vulnerability was reported by [email protected] and defenders should assess exposure and prioritize verification and updates to prevent exploitation.

Vendor
jeroenpeters1986
Product
Name Directory
CVSS
MEDIUM 6.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-16
Original CVE updated
2026-10-16
Advisory published
2026-10-16
Advisory updated
2026-10-16

Who should care

Defenders responsible for WordPress installations with the Name Directory plugin should assess exposure and prioritize verification and updates to prevent exploitation. Defenders should review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

The Name Directory plugin for WordPress has a Stored Cross-Site Scripting vulnerability, allowing authenticated attackers to inject arbitrary web scripts. Defenders should prioritize verification and updates to prevent exploitation.

  • Authenticated attackers with contributor-level access can inject arbitrary web scripts.
  • Injected scripts execute when a user accesses an injected page.
  • Defenders must verify and update the plugin to prevent exploitation.
  • Exposure requires verification from official sources.

Technical summary

The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'dir' Shortcode Attribute in all versions up to, and including, 1.34.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability was reported by [email protected] and defenders should prioritize verifying and updating the Name Directory plugin to prevent exploitation.

Defensive priority

Defenders should prioritize verifying and updating the Name Directory plugin to prevent exploitation.

Recommended defensive actions

  • Verify and update the Name Directory plugin to the latest version.
  • Restrict contributor-level access and above to trusted users.
  • Monitor for suspicious page access and script injection.
  • 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 vulnerability was reported by [email protected] and is documented in the CVE Program record and NVD vulnerability detail. The Name Directory plugin for WordPress has a Stored Cross-Site Scripting vulnerability via the 'dir' Shortcode Attribute in all versions up to, and including, 1.34.2 due to insufficient input sanitization and output escaping.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-104726 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-104726

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-104726 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-104726

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.