AddonsWordPress extension · Themerex
CVE-2024-13448
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 · uneditedThe ThemeREX Addons plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'trx_addons_uploads_save_data' function in all versions up to, and including, 2.32.3. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 ThemeREX Addons WordPress plugin fails to validate file types in its trx_addons_uploads_save_data function, permitting unauthenticated attackers to upload arbitrary files including executable scripts. This critical flaw enables complete server compromise through remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
AddonsWordPress extension
< 2.34.0CVSS 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.
-
Verify ThemeREX Addons plugin is installedCheck the WordPress plugin directory or access the Plugins admin page to confirm ThemeREX Addons is present and activeAffected if The plugin is installed and active on the WordPress site
-
Identify the installed version numberLocate the plugin version from the plugin header in the main plugin file, or view the version in the WordPress Plugins admin panelAffected if The version displayed is lower than 2.34.0 (for example, 2.33.x, 2.32.x, or earlier)
-
Confirm the vulnerable function existsInspect the plugin file containing the trx_addons_uploads_save_data function to verify the upload handling code is presentAffected if The function exists in the plugin files, indicating the upload capability is available
A user is affected if ThemeREX Addons is installed with a version lower than 2.34.0, as the plugin contains the vulnerable file upload function.
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 · scoped2.34.0
Update ThemeREX Addons to version 2.32.4 or later immediately; consider disabling the plugin or blocking upload endpoints at the web server level until the patch is applied.
ThemeREX Addons version 2.34.0 or later
- 1. Backup your WordPress site and database before making any changes
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- 3. Locate the ThemeREX Addons plugin in the list
- 4. Check if the current version is below 2.34.0 - if so, the site is vulnerable
- 5. Update the ThemeREX Addons plugin to version 2.34.0 or later
- 6. Verify the update was successful by checking the plugin version in the plugins list
- 7. Test that file upload functionality works as expected for legitimate users
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Addons
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13448 — 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-13448 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