CVE-2024-58349
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 Theme Travelscape 1.0.3 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious files by exploiting insufficient validation in the theme's upload functionality. Attackers can upload arbitrary files to the theme directory and execute them to achieve remote code execution on the affected WordPress installation.
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 Travelscape WordPress theme version 1.0.3 has an unauthenticated arbitrary file upload vulnerability in its upload functionality due to insufficient validation. Attackers can bypass validation checks to upload malicious PHP files to the theme directory and execute them for 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
- 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 Travelscape theme is installedIn WordPress admin, go to Appearance > Themes to list installed themes. Look for 'Travelscape' in the theme list. Click on the theme to view its details and confirm the version number displayed.Affected if Travelscape theme version 1.0.3 is active or installed on the WordPress site.
-
Inspect theme directory for unexpected filesNavigate to wp-content/themes/travelscape/ via FTP, file manager, or command line. List all files and subdirectories. Look for PHP files with random names, double extensions (e.g., image.php.jpg), or files modified recently outside normal update cycles.Affected if Unexpected PHP files exist in the theme directory that were not part of the original theme distribution.
-
Check upload directory configurationExamine the theme files for upload handling code. Look for functions that process file uploads and verify the destination path. Check if uploaded files are being saved within wp-content/themes/travelscape/ or its subdirectories.Affected if File uploads are being stored inside the theme directory rather than in wp-content/uploads/ or outside the web root.
-
Review access logs for upload activityExamine web server access logs (Apache error.log, access.log, or Nginx access.log) for POST requests to the theme's upload handler endpoint. Look for requests from unauthenticated IPs uploading files with .php extensions.Affected if Logs show unauthenticated POST requests uploading files, especially PHP files, to theme-related endpoints.
-
Verify file permission settingsCheck file permissions on the travelscape theme directory. The directory should not be writable by the web server user. Use 'ls -la' or file manager to view permissions.Affected if The theme directory has writable permissions (e.g., 755 with write access for group/others, or 775/777) allowing file creation.
A site is affected if Travelscape theme version 1.0.3 is installed and its upload functionality allows files to be placed within the theme directory where they can be executed as PHP.
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 dataDisable the vulnerable upload functionality immediately until a patched theme version is available, or implement proper server-side file type validation with allowlist filtering and rename uploaded files to prevent execution.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-58349 — 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-58349 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