# CVE-2026-123667: Photo Engine < 6.6.2 - Author+ Stored XSS via Keyword Names

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

The Photo Engine (Media Organizer & Lightroom) WordPress plugin before 6.6.2 does not sanitise and escape keyword names before storing them and outputting them on its debugging page, allowing users with the Author role and above to perform Stored Cross-Site Scripting attacks against administrators who have enabled that page.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Photo Engine (Media Organizer & Lightroom): ≥ 0; < 6.6.2 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-79

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/4dc2a8c5-9f1d-4bec-86fd-6d9b4aae5444/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/4dc2a8c5-9f1d-4bec-86fd-6d9b4aae5444/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-123667; retrieved 2026-11-11; source updated 2026-11-11

Revision: 879a53df5a2a7339afce94eced9c4eddcb3fe0eab1846fed24aa607527d98a4e

Canonical: https://y2.dev/cve/CVE-2026-123667

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.