CVE-2026-15965: MaxUpload <= 1.4.0 - Unauthenticated Arbitrary File Upload via 'resumableFilename' Parameter

Published Aug 15, 2026
·
Updated

The MaxUpload – Big File Uploads – Increase Maximum File Upload Size plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1.4.0 via the handleupload function. This is due to a filename-validation mismatch in the handleupload function where extension and MIME checks are applied to the uploaded chunk's filename but not to the final assembled filename derived from the resumableFilename parameter. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible.

Affected Software

1 affected component
MaxUpload Big File Uploads – Increase Maximum File Upload Size (WordPress plugin)<=1.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade WordPress MaxUpload – Big File Uploads – Increase Maximum File Upload Size plugin to a version that resolves this vulnerability.

    Fixed in 1.4.0

Event History

Aug 15, 2026
CVE Published
via MITRE·02:26 AM
Data Sourced
via MITRE·02:26 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-15965?

CVE-2026-15965 has a high severity rating of 8.8.

2

What type of vulnerability is CVE-2026-15965?

CVE-2026-15965 is classified as an Unauthenticated Arbitrary File Upload vulnerability.

3

How can I mitigate CVE-2026-15965?

To mitigate CVE-2026-15965, update the MaxUpload plugin to version 1.4.1 or later, which addresses the vulnerability.

4

Who is affected by CVE-2026-15965?

All users of the MaxUpload Big File Uploads plugin for WordPress up to and including version 1.4.0 are affected by CVE-2026-15965.

5

What causes CVE-2026-15965?

CVE-2026-15965 is caused by a filename-validation mismatch in the handle_upload function.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203