# CVE-2025-23771: WordPress Push Notification for Post and BuddyPress plugin <= 2.11 - Settings Change vulnerability

> An attacker can modify plugin settings without authorization due to missing access controls in the WordPress Push Notification for Post and BuddyPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2025
- **Updated:** 11 May 2026
- **Also known as:** GHSA-jw36-4vp7-rmq2

## What is CVE-2025-23771?

CVE-2025-23771 is a medium-severity missing authorization vulnerability in Murali Push Notification for Post and BuddyPress, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in Murali Push Notification for Post and BuddyPress push-notification-for-post-and-buddypress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Push Notification for Post and BuddyPress: from n/a through <= 2.11.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-23771?


## How do I fix CVE-2025-23771?

No fix has been published for CVE-2025-23771 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-23771 being exploited?

There is no known exploitation of CVE-2025-23771 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23771 and fix it if it is affected.

What it is: CVE-2025-23771 is a medium-severity missing authorization vulnerability in Murali Push Notification for Post and BuddyPress, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23771 in the wild and no public exploit code.

Affected product: Murali Push Notification for Post and BuddyPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23771/ (Markdown: https://insights.sbomify.com/CVE-2025-23771/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23771
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23771
- OSV: https://osv.dev/vulnerability/CVE-2025-23771

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23771/
Summaries are generated and may contain mistakes; the official description above is the record.