WPXPO PostX Plugin up to 4.1.35 on WordPress privileges assignment

Summaryinfo

A vulnerability was found in WPXPO PostX Plugin up to 4.1.35 on WordPress. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to privileges assignment. This vulnerability is listed as CVE-2025-55707. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in WPXPO PostX Plugin up to 4.1.35 on WordPress and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a privileges assignment vulnerability. Using CWE to declare the problem leads to CWE-266. A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Incorrect Privilege Assignment vulnerability in WPXPO PostX ultimate-post allows Privilege Escalation.This issue affects PostX: from n/a through <= 4.1.35.

The weakness was presented by Denver Jackson. The advisory is shared at vdp.patchstack.com. The identification of this vulnerability is CVE-2025-55707 since 08/14/2025. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/18/2025). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• WPXPO

Name

• PostX Plugin

Version

• 4.1.0
• 4.1.1
• 4.1.2
• 4.1.3
• 4.1.4
• 4.1.5
• 4.1.6
• 4.1.7
• 4.1.8
• 4.1.9
• 4.1.10
• 4.1.11
• 4.1.12
• 4.1.13
• 4.1.14
• 4.1.15
• 4.1.16
• 4.1.17
• 4.1.18
• 4.1.19
• 4.1.20
• 4.1.21
• 4.1.22
• 4.1.23
• 4.1.24
• 4.1.25
• 4.1.26
• 4.1.27
• 4.1.28
• 4.1.29
• 4.1.30
• 4.1.31
• 4.1.32
• 4.1.33
• 4.1.34
• 4.1.35

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion