azurecurve Shortcodes in Comments Plugin up to 2.0.2 on WordPress Shortcode do_shortcode code injection

Summaryinfo

A vulnerability has been found in azurecurve Shortcodes in Comments Plugin up to 2.0.2 on WordPress and classified as critical. Affected by this vulnerability is the function do_shortcode of the component Shortcode Handler. Performing a manipulation results in Remote Code Execution. This vulnerability was named CVE-2025-2809. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in azurecurve Shortcodes in Comments Plugin up to 2.0.2 on WordPress. This affects the function do_shortcode of the component Shortcode Handler. The manipulation with an unknown input leads to a remote code execution vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The azurecurve Shortcodes in Comments plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.0.2. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2025-2809 since 03/25/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/10/2025). MITRE ATT&CK project uses the attack technique T1059 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

• azurecurve

Name

• Shortcodes in Comments Plugin

Version

• 2.0.0
• 2.0.1
• 2.0.2

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