CVE-2025-9885 MEDIUM

CVE-2025-9885: MPWizard – Create Mercado Pago Payment Links <= 1.2.1 - Cross-Site Request Forgery to Arbitrary Post Deletion

Vendor Laudanumsoft
Product MPWizard – Create Mercado Pago Payment Links
Weakness CWE-352 · CSRF
Published October 3, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The MPWizard – Create Mercado Pago Payment Links plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.1. This is due to missing or incorrect nonce validation in the '/includes/admin/class-mpwizard-table.php' file. This makes it possible for unauthenticated attackers to delete arbitrary posts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

MPWizard – Create Mercado Pago Payment Links versions 1.2.1 and earlier contain a cross-site request forgery (CSRF) vulnerability. An attacker can craft a malicious link or page that, when visited by a logged-in site administrator, performs unwanted actions on the site without their knowledge. The vulnerability requires user interaction but does not require authentication to set up the attack.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into performing unwanted actions (like creating or modifying payment links) without their consent.

Potential impact on your site

04Site Impact

An attacker can modify payment link settings or create unauthorized Mercado Pago integrations if an admin is tricked into visiting a malicious page.

Conditions required to exploit

05Prerequisites

Admin must visit a malicious link or page while logged into the site; attacker has no special access requirements.

Key dates

06Disclosure timeline

October 3, 2025 CVE published
April 8, 2026 Record updated