CVE-2026-88997 JSM Show Post Metadata < 4.9.1 - Contributor+ Stored XSS via Custom Field Meta Key

Medium 6.8 Published Updated

Contributors can inject JavaScript via post meta keys, leading to session hijacking of higher-privileged users reviewing posts.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-88997?

CVE-2026-88997 is a medium-severity cross-site scripting vulnerability in Unknown JSM Show Post Metadata, published on 23 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

Official description

The JSM Show Post Metadata WordPress plugin before 4.9.1 does not properly escape a post meta key before outputting it into an inline event-handler attribute in an admin-facing meta box, allowing users with contributor-level access and above to inject arbitrary JavaScript that executes in the session of a higher-privileged user who reviews the affected post.

Weakness: CWE-79

Which versions are affected by CVE-2026-88997?

How do I fix CVE-2026-88997?

No fix has been published for CVE-2026-88997 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-88997 being exploited?

There is no known exploitation of CVE-2026-88997 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-w38r-xjmg-mmg7.

Is CVE-2026-88997 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free