Mkrapel Regiones Y Ciudades De Chile Para WcWordPress extension · Marketingrapel

CVE-2023-48781

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to after 4.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Marketing Rapel MkRapel Regiones y Ciudades de Chile para WC.This issue affects MkRapel Regiones y Ciudades de Chile para WC: from n/a through 4.3.0.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the MkRapel Regiones y Ciudades de Chile para WC WordPress plugin (versions through 4.3.0). The vulnerability allows attackers to trick authenticated users into unknowingly submitting malicious requests to the WordPress site, potentially modifying settings or performing unauthorized actions.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions within the plugin, and validate the nonce on the server side before processing any request.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mkrapel Regiones Y Ciudades De Chile Para WcWordPress extension
Affected:<= 4.3.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin installation directory
    Check the WordPress plugins folder (wp-content/plugins/) for a directory named 'mkrapel-regiones-y-ciudades-de-chile-para-wc' or similar containing 'mkrapel' or 'mkrapel-chile'
    Affected if The plugin directory exists in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named index.php or similar in the plugin directory) and locate the 'Version' header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry
    Affected if The version displayed is 4.3.0 or any version lower (e.g., 4.2.9, 4.0, etc.)
  3. Confirm the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or query the wp_options table for the option_name 'active_plugins' to see if the plugin is listed
    Affected if The plugin shows as 'Active' in the WordPress admin or is present in the active_plugins array
  4. Check for anti-CSRF token implementation (optional deeper inspection)
    Examine the plugin's PHP files for the presence of wp_nonce_field(), wp_create_nonce(), or verify_nonce() function calls on form handlers and AJAX actions
    Affected if No nonce verification functions are found in the plugin's form processing code (this indicates the CSRF vulnerability is present)

A user is affected if the MkRapel Regiones y Ciudades de Chile para WC plugin is installed, active, and running at version 4.3.0 or lower, with forms or AJAX actions lacking CSRF token validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.3.0
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions within the plugin, and validate the nonce on the server side before processing any request.

Fix this in Mkrapel Regiones Y Ciudades De Chile Para Wc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48781 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-48781 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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