dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10041

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Flex QR Code Generator plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in thesave_qr_code_to_db() function in all versions up to, and including, 1.2.5. 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 confidence

The Flex QR Code Generator WordPress plugin fails to validate file types in the save_qr_code_to_db() function, allowing unauthenticated attackers to upload arbitrary files to the server. This arbitrary file upload vulnerability can be chained to achieve remote code execution by uploading malicious PHP scripts or other executable content.

MitigationUpdate the plugin to version 1.2.6 or later; if no patch is available, disable the plugin immediately and consider deploying a WAF rule to block suspicious file uploads while investigating for Indicators of Compromise.

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 checks

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

  1. Verify Flex QR Code Generator plugin is installed
    Check for the plugin folder in wp-content/plugins/ or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if Flex QR Code Generator or flex-qr-code-generator appears in the list of installed plugins
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually flex-qr-code-generator.php) and locate the plugin header comment containing 'Version:' or check the WordPress plugins admin page
    Affected if Version is below 1.2.6 (versions prior to 1.2.6 lack proper file type validation)
  3. Locate the vulnerable save_qr_code_to_db function
    Search plugin files for the function 'save_qr_code_to_db' - typically found in the main plugin file or an includes/admin file handling QR code database operations
    Affected if The function exists in the installed plugin files without file type validation logic (look for absence of mime type or extension checks)
  4. Determine if unauthenticated file upload is exposed
    Examine AJAX hooks or form handlers that call save_qr_code_to_db - check for 'add_action("wp_ajax_' or 'add_action("wp_ajax_nopriv_' calls and verify if nopriv (unauthenticated) access is permitted
    Affected if The file upload endpoint is accessible to unauthenticated users (wp_ajax_nopriv or no auth check found)

You are affected if Flex QR Code Generator plugin is installed, the version is below 1.2.6, and the save_qr_code_to_db function is exposed without proper file type validation and without authentication requirements.

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 plugin to version 1.2.6 or later; if no patch is available, disable the plugin immediately and consider deploying a WAF rule to block suspicious file uploads while investigating for Indicators of Compromise.

Recommended fix Moderate confidence

Flex QR Code Generator version 1.2.6 or latest release

  1. Check the WordPress admin panel for plugin updates under Dashboard > Updates
  2. Update Flex QR Code Generator plugin to the latest available version
  3. If automatic updates are enabled, verify the plugin has updated to version 1.2.6 or later
  4. Confirm the update was successful by checking the plugin version in Plugins > Installed Plugins

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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