dbcve.org
Big File UploadsWordPress extension · Infiniteuploads

CVE-2023-47792

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 2.1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Infinite Uploads Big File Uploads – Increase Maximum File Upload Size plugin <= 2.1.1 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Infinite Uploads WordPress plugin allows attackers to trick authenticated administrators into submitting unintended requests that modify plugin settings or trigger actions, due to missing or improper nonce validation on sensitive form submissions and AJAX endpoints.

MitigationUpdate the Infinite Uploads Big File Uploads plugin to version 2.1.2 or later. If no update is available, disable the plugin until a patched version is released.

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
Big File UploadsWordPress extension
Affected:< 2.1.2

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Confirm Infinite Uploads plugin is installed
    Log in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Infinite Uploads' or 'Big File Uploads' in the plugins list
    Affected if The plugin does not appear in the installed plugins list - then you are NOT affected
  2. Identify the installed version number
    In the Plugins list, locate the Infinite Uploads plugin entry and look for the version number displayed beneath the plugin name
    Affected if No version number is displayed or the plugin is not found - you may need to check plugin files directly via file system or contact the site administrator
  3. Compare version against the affected range
    Check if the installed version is less than 2.1.2. Version 2.1.2 and later are patched. For example, versions like 2.1.1, 2.0.x, 1.x.x are all vulnerable.
    Affected if The installed version is 2.1.1 or lower - you ARE affected by this vulnerability
  4. Verify admin access exists
    Confirm you have administrator-level access to the WordPress site, as the CSRF vulnerability targets authenticated administrators
    Affected if You do not have admin access, the vulnerability cannot be exploited against your session - but the unpatched plugin still poses a risk

You are affected if the Infinite Uploads Big File Uploads plugin version is 2.1.1 or lower (less than 2.1.2).

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
Upgrade available Upgrade to 2.1.2 or later
Fixed in 2.1.2
Interim mitigation

Update the Infinite Uploads Big File Uploads plugin to version 2.1.2 or later. If no update is available, disable the plugin until a patched version is released.

Recommended fix High confidence

2.1.2

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find the 'Infinite Uploads Big File Uploads' plugin (also listed as 'Big File Uploads')
  4. Click 'Update now' if an update is available, or manually update to version 2.1.2 or later
  5. Verify the plugin is running version 2.1.2 or higher after the update
  6. Test that file upload functionality continues to work correctly

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

Fix this in Big File Uploads Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47792 — 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-2023-47792 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