# CVE-2024-10728: PostX <= 4.1.16 - Missing Authorization to Arbitrary Plugin Installation/Activation

> Authenticated subscribers can install and activate arbitrary plugins due to missing capability checks, potentially leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-h7j2-r3qv-9q3v

## What is CVE-2024-10728?

CVE-2024-10728 is a high-severity missing authorization vulnerability in wpxpo Post Grid Gutenberg Blocks for News, Magazines, Blog Websites – PostX, published on 16 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Post Grid Gutenberg Blocks and WordPress Blog Plugin – PostX plugin for WordPress is vulnerable to unauthorized plugin installation/activation due to a missing capability check on the 'install_required_plugin_callback' function in all versions up to, and including, 4.1.16. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-10728?

It affects 1 product.


Products: Wpxpo Postx.

## How do I fix CVE-2024-10728?

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

## Is CVE-2024-10728 being exploited?

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

Public exploit code:

- PostX <= 4.1.16 - Missing Authorization to Arbitrary Plugin Installation/Activation (github_poc): https://github.com/RandomRobbieBF/CVE-2024-10728

## Other vulnerabilities in wpxpo Post Grid Gutenberg Blocks for News, Magazines, Blog Websites – PostX

- [CVE-2023-36385](https://insights.sbomify.com/CVE-2023-36385/): WordPress PostX – Gutenberg Blocks for Post Grid Plugin <= 2.9.9 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2024-4305](https://insights.sbomify.com/CVE-2024-4305/): PostX < 4.1.0 - Contributor+ Stored XSS (medium 6.8)
- [CVE-2024-50443](https://insights.sbomify.com/CVE-2024-50443/): WordPress PostX plugin <= 4.1.12 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2023-3992](https://insights.sbomify.com/CVE-2023-3992/): PostX - Gutenberg Post Grid Blocks < 3.0.6 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2024-31246](https://insights.sbomify.com/CVE-2024-31246/): WordPress PostX plugin <= 3.2.3 - Author+ Post/Page Duplication vulnerability (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10728 and fix it if it is affected.

What it is: CVE-2024-10728 is a high-severity missing authorization vulnerability in wpxpo Post Grid Gutenberg Blocks for News, Magazines, Blog Websites – PostX, published on 16 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10728 in the wild and no public exploit code.

Affected product: wpxpo Post Grid Gutenberg Blocks for News, Magazines, Blog Websites – PostX. 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-2024-10728/ (Markdown: https://insights.sbomify.com/CVE-2024-10728/index.md)
```

## Sources

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

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