CVE-2025-23659
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in hernanjh MercadoLibre Integration mercadolibre-integration allows Stored XSS.This issue affects MercadoLibre Integration: from n/a through <= 1.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA CSRF vulnerability in the MercadoLibre Integration WordPress plugin allows authenticated attackers to craft malicious requests that result in Stored XSS. The plugin lacks proper anti-CSRF token validation on state-changing operations, enabling attackers to inject persistent malicious scripts through form submissions or AJAX actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if MercadoLibre Integration plugin is installedGo to WordPress admin > Plugins and look for 'MercadoLibre Integration' in the installed plugins list, or search the wp-content/plugins directory for a folder named 'mercadolibre' or similarAffected if The plugin is installed and active
-
Determine the installed plugin versionIn WordPress admin > Plugins, click on the MercadoLibre Integration plugin to view its details, or read the 'readme.txt' or main PHP file in the plugin folder to find the 'Version:' headerAffected if The version is unknown or falls within any affected version range (if published)
-
Inspect plugin forms for anti-CSRF nonce fieldsView the source code of any frontend or admin forms rendered by the plugin (e.g., settings forms, submission forms). Look for HTML input fields named '_wpnonce', 'nonce', or similar containing a token valueAffected if Forms lack a nonce field or token input, meaning CSRF protection is missing
-
Check AJAX endpoints for nonce verificationExamine the plugin PHP code for AJAX handlers (admin-ajax.php calls or wp_ajax_ hooks). Look for calls to 'wp_verify_nonce()' or 'check_ajax_referer()' within these handlersAffected if AJAX actions do not verify nonces before processing state-changing requests
-
Search for stored XSS payloads in plugin-stored dataCheck the WordPress database (wp_posts, wp_postmeta, or plugin-specific tables) for suspicious script tags, iframe tags, or event handlers (onerror, onload, etc.) in data that originated from plugin forms or AJAX submissionsAffected if Malicious scripts are found stored in the database via plugin functionality
If the MercadoLibre Integration plugin is installed and its forms or AJAX endpoints lack nonce verification (CSRF protection), the environment is vulnerable to stored XSS via CSRF attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens (nonces) on all forms and AJAX endpoints, validate them server-side, and apply proper input sanitization plus output encoding to prevent stored XSS.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23659 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data