Skip to main content
Menu
CVEs

pmo-platform stored XSS in eval viewer via unescaped JSON

CVE-2026-77349Published , updated

5.0MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.69.1
Who is exposed
Not reported

Summary

The pmo-platform Eval Viewer has a stored cross-site scripting flaw: crafted output in the workspace run folders can break out of an inline script and run JavaScript when an operator generates and opens the viewer. An attacker with local access and no login can use this to read embedded prompts and outputs, change the viewer page, or modify saved feedback.

Written by a model

Original description

pmo-platform is a modular PMO and release-management platform for Claude Code. From 3.48 until 3.69.1, release/skills/pmo-skill-refiner/eval-viewer/generate_review.py reads untrusted model or skill output from workspace/run*/outputs/ and embeds it with json.dumps into viewer.html inside an inline script without escaping HTML metacharacters. A crafted output can close the script element and execute JavaScript when an operator generates and opens the viewer. The maintainer also confirmed that DOM-based injection through renderGrades and renderBenchmark innerHTML survives transport-only escaping, so affected render sinks must neutralize the content. Executed script can read embedded prompts and outputs, alter the viewer DOM, or modify saved feedback. This issue is fixed in version 3.69.1.

What to do

Upgrade to a fixed version: 3.69.1.

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-77349 (pmo-platform: Stored XSS in Eval Viewer via Unescaped JSON Embedded in Script Context), 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-77349 (entry last updated 2026-11-20):
Affected:
- cody-hutson pmo-platform: from 3.48, fixed in 3.69.1
Fixed versions: 3.69.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77349 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77349 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://github.com/cody-hutson/pmo-platform/security/advisories/GHSA-rw36-5pf9-w2vc
- https://github.com/cody-hutson/pmo-platform/commit/eb90e6772a446997a04d42edd624a915af35b1b7
- https://github.com/cody-hutson/pmo-platform/releases/tag/v3.69.1
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-77349
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-77349"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5/10CVSS 5.0
  • No patch0/5No signal

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

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

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

  4. Record last updated

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · cody-hutson/pmo-platform · Advisory GHSA-rw36-5pf9-w2vc
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77349
RecordNVD · CVE-2026-77349
Other links 2
RepositoryGitHub · cody-hutson/pmo-platform · Commit eb90e677
RepositoryGitHub · cody-hutson/pmo-platform · Release v3.69.1

Questions about CVE-2026-77349

Is CVE-2026-77349 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77349?

pmo-platform: from 3.48 before 3.69.1.

Source: cve.now feed data

How do I fix CVE-2026-77349?

Upgrade to a fixed version: 3.69.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.