dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-11427

MEDIUM · 5.8 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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 WP Migrate Lite – WordPress Migration Made Easy plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.7.6 via the wpmdb_flush AJAX action. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to obtain information about internal services.

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 WP Migrate Lite WordPress plugin contains a blind Server-Side Request Forgery (SSRF) vulnerability in the wpmdb_flush AJAX action. This allows unauthenticated attackers to cause the web server to make arbitrary HTTP requests to internal or external resources, potentially revealing information about internal services and infrastructure.

MitigationUpdate WP Migrate Lite to version 2.7.7 or later. Additionally, implement access controls to block unauthenticated access to the wpmdb_flush AJAX action until the patch is applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 WP Migrate Lite is installed
    Check WordPress plugins directory or admin panel for WP Migrate Lite plugin presence
    Affected if WP Migrate Lite plugin is installed
  2. Check installed version number
    Access WordPress admin under Plugins > Installed Plugins and locate WP Migrate Lite version, or inspect plugin header file in wp-content/plugins/wp-migrate-wp-migrate-lite/
    Affected if Version is below 2.7.7 (vulnerable)
  3. Test wpmdb_flush AJAX action accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=wpmdb_flush parameter and verify if the endpoint responds without authentication
    Affected if Endpoint is reachable without authentication (vulnerable configuration)

You are affected if WP Migrate Lite version below 2.7.7 is installed and the wpmdb_flush AJAX action accepts unauthenticated requests.

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 WP Migrate Lite to version 2.7.7 or later. Additionally, implement access controls to block unauthenticated access to the wpmdb_flush AJAX action until the patch is applied.

Recommended fix Moderate confidence

Latest version after 2.7.6 (check wordpress.org for current release)

  1. Go to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate "WP Migrate Lite – WordPress Migration Made Easy"
  4. Check if the current version is 2.7.6 or lower
  5. If vulnerable, click "Update Now" to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/wp-migrate and upload manually

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11427 — 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-11427 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