dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-1969

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The trx_addons WordPress plugin before 2.38.5 does not correctly validate file types in one of its AJAX action, allowing unauthenticated users to upload arbitrary file. This is due to an incorrect fix of CVE-2024-13448

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 confidence

The trx_addons WordPress plugin before version 2.38.5 contains a file upload vulnerability in one of its AJAX actions due to improper file type validation. Unauthenticated attackers can exploit this to upload arbitrary files to the server, representing a security control bypass of the previous CVE-2024-13448 fix.

MitigationUpdate the trx_addons plugin to version 2.38.5 or later to apply the corrected file type validation fix. If immediate update is not possible, consider disabling the affected AJAX endpoint or implementing web application firewall rules to restrict file uploads.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify trx_addons plugin is installed
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and locate trx_addons in the list. Note the version number displayed under the plugin name.
    Affected if The plugin is present with any version below 2.38.5
  2. Confirm the installed version number
    Compare the installed version to the affected range: versions before 2.38.5 are vulnerable. The version is displayed in the plugin list or can be checked in the plugin header files via file manager or FTP.
    Affected if Installed version is lower than 2.38.5 (for example, 2.38.4, 2.38.0, 2.37.x, etc.)
  3. Identify accessible AJAX endpoints
    Review the plugin code for registered AJAX actions, particularly those handling file uploads. Check wp_ajax and wp_ajax_nopriv hooks. Look for handlers that process file upload requests.
    Affected if The file upload AJAX handler is registered and accessible (especially to unauthenticated users via wp_ajax_nopriv)
  4. Check if file upload functionality is enabled
    Inspect the plugin settings in WordPress admin under the trx_addons plugin options. Look for any toggles or settings related to file uploads, media handling, or content import features.
    Affected if File upload functionality is enabled in the plugin configuration

You are affected if the trx_addons plugin is installed with a version lower than 2.38.5 and the vulnerable AJAX endpoint for file uploads is accessible and enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the trx_addons plugin to version 2.38.5 or later to apply the corrected file type validation fix. If immediate update is not possible, consider disabling the affected AJAX endpoint or implementing web application firewall rules to restrict file uploads.

Recommended fix High confidence

trx_addons plugin version 2.38.5 or later

  1. 1. Identify the current version of the trx_addons plugin installed on your WordPress site by navigating to Plugins > Installed Plugins in the WordPress admin dashboard
  2. 2. If the installed version is before 2.38.5, create a full backup of your WordPress site including the database and all files
  3. 3. Update the trx_addons plugin to version 2.38.5 or later by going to Dashboard > Updates or the Plugins page and applying the available update
  4. 4. Alternatively, you can manually upload the updated plugin by downloading version 2.38.5 or the latest version from the WordPress Plugin Repository and installing via Plugins > Add New > Upload Plugin
  5. 5. After updating, verify the new version number reflects 2.38.5 or higher
  6. 6. Test the AJAX functionality that handles file uploads to ensure the plugin continues to work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1969 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1969 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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