CVE-2025-49447
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 Fastw3b LLC FW Food Menu allows Using Malicious Files. This issue affects FW Food Menu : from n/a through 6.0.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 confidenceUnrestricted file upload vulnerability in FW Food Menu plugin allows authenticated attackers to upload malicious files (e.g., PHP webshells) to the server, potentially achieving remote code execution. The plugin fails to properly validate file types or restrict dangerous extensions during the upload process.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 FW Food Menu plugin is installedCheck WordPress plugins directory (wp-content/plugins/) for fw-food-menu folder, or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if The FW Food Menu plugin is present in the WordPress installation
-
Identify plugin versionLocate the main plugin PHP file (often fw-food-menu.php) and look for a version comment or constant, or check the plugin header in WordPress admin plugin listAffected if Unable to verify the version or version is unknown (no fixed version range provided for this CVE)
-
Locate plugin file upload functionalitySearch plugin directory for upload-related files (upload.php, handle_upload, $_FILES, move_uploaded_file) or check for menu item endpoints that accept file uploadsAffected if The plugin contains file upload handling code that processes user-submitted files
-
Inspect upload directory configurationCheck the wp-content/uploads directory for .htaccess file and server configuration; verify if directory listing is enabled and examine file permissionsAffected if Upload directory allows file storage without restrictive configuration
-
Verify PHP execution is permitted in uploadsExamine .htaccess in wp-content/uploads for PHP execution rules; if no .htaccess exists or PHP handler is not explicitly disabled, PHP files can executeAffected if PHP execution is not blocked in the uploads directory (no DisableHandlers or similar restrictions)
-
Scan for suspicious uploaded filesUse find or file manager to search wp-content/uploads and subdirectories for .php, .phtml, .php5, .exe, or other executable extensions; review file creation timestampsAffected if Unknown PHP files or suspicious executables exist in upload directories
User is affected if FW Food Menu plugin is installed and the upload functionality is accessible without proper file type validation, with PHP execution allowed in the uploads directory.
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 restrict file upload permissions to trusted administrators only, disable PHP execution in upload directories via .htaccess or server config, and monitor for suspicious uploads. Consider disabling the plugin until vendor patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49447 — 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-2025-49447 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