CVE-2024-58348
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 · uneditedWordPress Background Image Cropper version 1.2 contains a remote code execution vulnerability that allows unauthenticated attackers to upload arbitrary files by accessing the ups.php endpoint. Attackers can upload PHP files through the file upload form in the plugin directory to execute arbitrary code on the server.
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 confidenceThe WordPress Background Image Cropper plugin version 1.2 contains an unauthenticated arbitrary file upload vulnerability in the ups.php endpoint, allowing remote attackers to upload and execute malicious PHP files for complete server compromise.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WordPress Background Image Cropper plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Background Image Cropper' in the list of active or inactive plugins.Affected if The plugin appears in the installed plugins list regardless of activation status
-
Identify the installed plugin versionIn the WordPress plugins list, click on the plugin name or view the plugin files. Open the main plugin PHP file (usually named similarly to the plugin directory) and look for a version comment or header that states 'Version: X.X'Affected if The version is 1.2 exactly, or if you cannot determine the version and the plugin is present
-
Verify the vulnerable ups.php endpoint existsUsing a web browser or curl command, attempt to access the ups.php file directly at the expected path: /wp-content/plugins/background-image-cropper/ups.php or /wp-content/plugins/background-image-cropper/includes/ups.phpAffected if The endpoint returns a response (200 OK) rather than a 404 Not Found error, indicating the file exists and is accessible
-
Check for suspicious PHP files in upload directoriesExamine the wp-content/uploads directory and any plugin-specific upload folders for unexpected .php files. Use file system commands: find /path/to/wp-content/uploads -name '*.php' -mtime -30 to find recently modified PHP files.Affected if Any PHP files exist in upload directories, especially recently created ones, as the vulnerability allows arbitrary PHP uploads
-
Review server access logs for ups.php accessCheck web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for any GET or POST requests to the ups.php endpoint from IP addresses you do not recognize.Affected if There are any unauthenticated requests to ups.php in the logs, indicating potential exploitation attempts
You are affected if the WordPress Background Image Cropper plugin version 1.2 is installed and the ups.php endpoint is accessible, as this combination enables unauthenticated attackers to upload and execute arbitrary PHP code.
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 dataImmediately remove or disable the vulnerable plugin until an official security patch is available, or upgrade to a patched version if released.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-58348 — 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-2024-58348 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