dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-1502

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The IP2Location Redirection plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'download_ip2location_redirection_backup' AJAX action in all versions up to, and including, 1.33.3. This makes it possible for unauthenticated attackers to download the plugin's settings.

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 · high confidence

The IP2Location Redirection WordPress plugin has a Broken Access Control vulnerability where the AJAX action 'download_ip2location_redirection_backup' lacks a capability check. This allows unauthenticated users to trigger the action and download the plugin's settings/configuration data.

MitigationUpdate the plugin to version 1.34 or later which includes proper capability verification on the AJAX action. If no update is available, consider disabling the plugin until a patch is released.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Confirm IP2Location Redirection plugin is installed
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'ip2location-redirection' or 'ip2location-redirection-wordpress-plugin', or look in the WordPress admin under Plugins > Installed Plugins
    Affected if The IP2Location Redirection plugin is present in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin file (usually plugin-name.php in the plugin folder) and look for the 'Version:' header in the plugin comments, or check the WordPress admin plugin list
    Affected if The installed version is lower than 1.34 (versions before the security fix)
  3. Test unauthenticated AJAX access to the vulnerable action
    Send a POST request to your site's /wp-admin/admin-ajax.php with action=download_ip2location_redirection_backup (no authentication required). Check if the response contains plugin configuration data, SQL export, or settings in JSON/CSV format
    Affected if The AJAX endpoint returns plugin configuration data or a valid backup file without requiring login credentials
  4. Verify the WordPress site configuration
    Confirm the site has user registration open or allows unauthenticated access to wp-admin/admin-ajax.php endpoints (default WordPress behavior)
    Affected if The site permits unauthenticated requests to admin-ajax.php (standard default configuration)

A user is affected if the IP2Location Redirection plugin version is below 1.34 AND the vulnerable AJAX action returns plugin configuration data without authentication.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.34 or later which includes proper capability verification on the AJAX action. If no update is available, consider disabling the plugin until a patch is released.

Recommended fix Moderate confidence

Version 1.33.4 or later (the first version after 1.33.3 that includes the security patch)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the IP2Location Redirection plugin
  4. Check if an update is available and update to the latest version
  5. Verify the update is to version 1.33.4 or higher which should contain the authorization fix

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2025-1502 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