CVE-2024-56264
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Beee ACF City Selector acf-city-selector allows Upload a Web Shell to a Web Server.This issue affects ACF City Selector: from n/a through <= 1.14.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 confidenceThe ACF City Selector WordPress plugin contains an unrestricted file upload vulnerability that allows attackers to upload dangerous file types, specifically PHP files containing web shells, directly to the web server. This can lead to remote code execution.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
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.
-
Verify ACF City Selector plugin is installedLog into WordPress admin, go to Plugins > Installed Plugins, and look for 'ACF City Selector' in the list. Alternatively, check the /wp-content/plugins/ directory for the acf-city-selector folder.Affected if The plugin is installed and active
-
Identify the installed plugin versionIn WordPress admin, click on the plugin name to view details and find the version number. Or open the main plugin file (acf-city-selector.php) and look for the Version header comment.Affected if The version is older than the patched version (check WordPress plugin repository for current safe version)
-
Check if upload functionality is accessibleNavigate to the plugin settings or any City Selector admin page that handles CSV file imports. The vulnerability occurs in the city import feature that accepts file uploads.Affected if The plugin upload/import feature is enabled and accessible to users with contributor or higher roles
-
Inspect upload directories for suspicious filesCheck the /wp-content/uploads/ directory (or custom upload path) for newly created .php files, especially shell scripts (e.g., shell.php, backdoor.php, assert.php). Use file search: find /wp-content/uploads -name "*.php" -mtime -30Affected if Unexpected PHP files exist in upload directories, particularly with recent modification dates
-
Review web server access logs for file upload patternsSearch web server logs (access.log) for POST requests to /wp-admin/admin-ajax.php or the plugin's upload endpoint that include .php file extensions in the request.Affected if Logs show PHP files being uploaded through the plugin interface
-
Check for unauthorized admin accounts or malicious codeIn WordPress admin, go to Users > All Users and look for unknown admin accounts. Also check theme functions.php and plugin files for base64_decode, eval, or shell_exec calls.Affected if New admin accounts exist or suspicious PHP code is present in theme/plugin files
You are affected if the ACF City Selector plugin is installed, the upload/import feature is enabled, and either suspicious PHP files exist in upload directories or anomalous upload requests appear in logs.
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.
dbcve · scopedUpdate to the latest patched version of ACF City Selector. If no patch is available, disable the plugin's upload functionality, implement server-side file type validation with allowlist, and store uploaded files outside the webroot.
ACF City Selector version 1.14.1 or later (latest version available)
- 1. Check the current installed version of the ACF City Selector plugin in your WordPress installation
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. If the plugin version is 1.14.0 or lower, update to the latest available version of ACF City Selector
- 4. Alternatively, update via WordPress admin: Go to Dashboard > Updates and update the plugin if an update is available
- 5. Alternatively, manually update by downloading the latest version from the WordPress plugin repository and uploading via FTP or WordPress upload
- 6. After updating, verify the file upload functionality works correctly and test that malicious file types are properly blocked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56264 — 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-56264 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