Summaryinfo

A vulnerability has been found in PluXml up to 5.8.22 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Anti Spam-Captcha. This manipulation causes an unknown weakness. This vulnerability is registered as CVE-2025-70129. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability has been found in PluXml up to 5.8.22 and classified as problematic. Affected by this vulnerability is an unknown part of the component Anti Spam-Captcha. The CWE definition for the vulnerability is CWE-804. The product uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor. As an impact it is known to affect integrity. The summary by CVE is:

If the anti spam-captcha functionality in PluXml versions 5.8.22 and earlier is enabled, a captcha challenge is generated with a format that can be automatically recognized for articles, such that an automated script is able to solve this anti-spam mechanism trivially and publish spam comments. The details of captcha challenge are exposed within document body of articles with comments & anti spam-captcha functionalities enabled, including "capcha-letter", "capcha-word" and "capcha-token" which can be used to construct a valid post request to publish a comment. As such, attackers can flood articles with automated spam comments, especially if there are no other web defenses available.

The advisory is shared at youtu.be. This vulnerability is known as CVE-2025-70129 since 01/09/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 03/15/2026).

The vulnerability scanner Nessus provides a plugin with the ID 302206 (Linux Distros Unpatched Vulnerability : CVE-2025-70129), which helps to determine the existence of the flaw in a target environment.

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

The vulnerability is also documented in the vulnerability database at Tenable (302206). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• PluXml

Version

• 5.8.0
• 5.8.1
• 5.8.2
• 5.8.3
• 5.8.4
• 5.8.5
• 5.8.6
• 5.8.7
• 5.8.8
• 5.8.9
• 5.8.10
• 5.8.11
• 5.8.12
• 5.8.13
• 5.8.14
• 5.8.15
• 5.8.16
• 5.8.17
• 5.8.18
• 5.8.19
• 5.8.20
• 5.8.21
• 5.8.22

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

Video

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion