dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-3551

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Penci Soledad Data Migrator plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.3.0 via the 'data' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. This is limited to just PHP files.

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 Penci Soledad Data Migrator WordPress plugin versions up to 1.3.0 contains a Local File Inclusion vulnerability via the 'data' parameter, allowing unauthenticated attackers to include and execute arbitrary PHP files on the server. This enables complete code execution and potential bypass of access controls.

MitigationUpdate the Penci Soledad Data Migrator plugin to version 1.3.1 or later. If immediate patching is not possible, disable the plugin until an update can be 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Penci Soledad Data Migrator' in the list, or search the /wp-content/plugins/ directory for a folder named 'penci-soledad-data-migrator'
    Affected if The plugin is present on the WordPress installation
  2. Identify installed version
    In WordPress admin, click on the plugin to view details and note the version number displayed, or read the main plugin PHP file header which contains the Version field
    Affected if The version is 1.3.0 or lower (any version up to and including 1.3.0)
  3. Verify vulnerable endpoint accessibility
    Check if the file /wp-content/plugins/penci-soledad-data-migrator/inc/migrator.php or similar includes a 'data' parameter handler, or attempt a test request to the plugin's AJAX endpoint that handles migration data
    Affected if The plugin processes a 'data' parameter without proper validation and the migrator functionality is exposed
  4. Confirm unauthenticated access possibility
    Test accessing the migration functionality without authentication cookies or WP credentials to verify if the LFI can be triggered without being logged in
    Affected if The vulnerable endpoint is accessible to unauthenticated users (no login required)
  5. Check for evidence of exploitation
    Review web server access logs for unusual include(), require(), or file_get_contents() calls with user-supplied paths pointing to plugin directories, or check for new suspicious PHP files in unexpected locations
    Affected if Logs show LFI attempts targeting this plugin or suspicious PHP files exist on the server

A user is affected if the Penci Soledad Data Migrator plugin is installed with version 1.3.0 or lower and the migration functionality is accessible, allowing unauthenticated attackers to include arbitrary files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Penci Soledad Data Migrator plugin to version 1.3.1 or later. If immediate patching is not possible, disable the plugin until an update can be applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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