CVE-2024-10728: PostX <= 4.1.16 - Missing Authorization to Arbitrary Plugin Installation/Activation
Noroxi assessment
Priority: Plan (action score 47/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 39% (FIRST EPSS); higher than 98.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- No fixed version is recorded, but the references include a patch (commit or PR) link.
Add it to your regular patch cycle. See the fix and affected versions sections below.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 16, 2024
- Updated
- Jun 17, 2026
- EPSS
- 39.0% · 98th percentile
- CWE
- CWE-862
Report tools
Action score
47
Plan
Add it to your regular patch cycle.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 12 / 30 · 39.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Wordfence
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Is Post Grid Blocks & Templates for News, Magazine, & Blog Sites – PostX on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wpxpo | postx | cpe:2.3:a:wpxpo:postx |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wpxpo postxbefore 4.1.17
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Wordfence). Independent of NVD's CPE analysis and usually ahead of it.
wpxpo Post Grid Gutenberg Blocks for News, Magazines, Blog Websites – PostX
- up to and including 4.1.16affected · semver
Same product
wpxpo: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-31246WordPress PostX plugin <= 3.2.3 - Author+ Post/Page Duplication vulnerability35Monitor
- CVE-2025-69313WordPress PostX plugin <= 5.0.3 - Broken Access Control vulnerability30Monitor
- CVE-2025-55707WordPress PostX Plugin <= 4.1.35 - Privilege Escalation Vulnerability28Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-4305Jun 17, 2024 · PostX < 4.1.0 - Contributor+ Stored XSS27Monitor
- ← EarlierCVE-2024-50443Oct 28, 2024 · WordPress PostX plugin <= 4.1.12 - Cross Site Scripting (XSS) vulnerability21Monitor
- Later →CVE-2024-50513Nov 19, 2024 · WordPress PostX plugin <= 4.1.15 - Cross Site Scripting (XSS) vulnerability23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2024-11-16 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoCsame day
- Published
- TodayNov 10, 2026+725 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Sean Murphyfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-31246160 days apartWordPress PostX plugin <= 3.2.3 - Author+ Post/Page Duplication vulnerability35Monitor
- CVE-2025-69313432 days apartWordPress PostX plugin <= 5.0.3 - Broken Access Control vulnerability30Monitor
- CVE-2025-54751397 days apartWordPress PostX plugin <= 4.1.36 - Broken Access Control vulnerability28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-862 · Missing AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (4 more)Show less
- plugins.trac.wordpress.org/browser/ultimate-post/tags/4.1.16/classes/Initialization.php#L330
- plugins.trac.wordpress.org/changeset/3188636/ultimate-post/trunk/classes/Importer.php
- wordpress.org/plugins/ultimate-post/
- www.wordfence.com/threat-intel/vulnerabilities/id/076f36fb-c2fb-43e0-a027-1351d3995489?source=cve
Vendor advisories and official records. Exploit/PoC links are deliberately left out.