CVE-2024-50493
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 masterhomepage Automatic Translation automatic-translation allows Upload a Web Shell to a Web Server.This issue affects Automatic Translation: from n/a through <= 1.0.4.
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 the masterhomepage Automatic Translation plugin (versions <= 1.0.4) allows unauthenticated attackers to upload dangerous file types, specifically web shells, enabling remote code execution on the web server.
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.
-
Identify masterhomepage plugin installation and versionAccess your CMS plugin management interface or inspect the plugin directory to determine if masterhomepage is installed and retrieve its version numberAffected if The plugin version is 1.0.4 or lower (no fixed version noted)
-
Verify Automatic Translation feature statusLocate the plugin settings panel and check whether the Automatic Translation component is enabled or actively in useAffected if Automatic Translation is turned on or configured in the plugin settings
-
Locate upload directory configurationInspect the plugin configuration files or settings to identify the designated upload directory path used by the Automatic Translation featureAffected if An upload directory is configured and exists within the webroot
-
Confirm upload directory is web-accessibleDetermine whether the identified upload directory is served by the web server and accessible via HTTP requestsAffected if The upload directory can be reached through a web browser or HTTP tool
-
Scan upload directory for unexpected PHP filesList all files in the upload directory and examine for any PHP files, especially those with suspicious names or recent creation timestampsAffected if Any PHP files are present in the upload directory, as the plugin should not permit PHP uploads
You are affected if the masterhomepage plugin version is 1.0.4 or below, the Automatic Translation feature is enabled, and your upload directory is web-accessible with any PHP files present.
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 dataImplement strict allowlist-based file type validation, store uploaded files outside web root, disable script execution in upload directories, and if a patched version exists, upgrade immediately.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50493 — 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-50493 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