dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-12673

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-06
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 the update_qr_code() function in all versions up to, and including, 1.2.7. 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 (versions up to 1.2.7) contains an unauthenticated arbitrary file upload vulnerability in the update_qr_code() function. Due to missing file type validation, attackers can upload malicious files to the server, potentially achieving remote code execution.

MitigationUpdate to the latest version of the plugin once available, or disable and remove the plugin until a patch is released. Consider deploying a WAF rule to block suspicious file upload requests to /wp-admin/admin-ajax.php endpoints.

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. Confirm plugin installation
    Check if the Flex QR Code Generator plugin exists in the WordPress plugins directory at wp-content/plugins/. Look for a folder named 'flex-qr-code-generator' or similar.
    Affected if The plugin folder exists in the WordPress installation's plugin directory.
  2. Identify installed plugin version
    Open the plugin's main PHP file (usually flex-qr-code-generator.php) or the readme.txt file in the plugin folder and locate the Version header comment.
    Affected if The installed version is 1.2.7 or any version up to and including 1.2.7.
  3. Verify vulnerable endpoint accessibility
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php is accessible and responds to requests with the action parameter set to 'update_qr_code'. This can be tested via a simple HTTP request to the endpoint.
    Affected if The site responds to unauthenticated requests to admin-ajax.php with action=update_qr_code and accepts file uploads.
  4. Inspect upload directory permissions
    Check the wp-content/uploads/ directory (or custom upload directory) and verify if it is writable by the web server. In WordPress admin, navigate to Media > Add New to test upload capability.
    Affected if The uploads directory is writable, allowing arbitrary file uploads via the vulnerable function.
  5. Review server access logs
    Search web server access logs (Apache/nginx) for POST requests to /wp-admin/admin-ajax.php with action=update_qr_code or similar upload-related actions from the plugin, focusing on requests with unusual file extensions.
    Affected if Unusual or malicious file types (non-image formats like .php, .phtml, .exe) appear in upload requests to the plugin's AJAX endpoint.

If the Flex QR Code Generator plugin version 1.2.7 or lower is installed and the site allows unauthenticated file uploads via admin-ajax.php, the environment is affected by this vulnerability.

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 to the latest version of the plugin once available, or disable and remove the plugin until a patch is released. Consider deploying a WAF rule to block suspicious file upload requests to /wp-admin/admin-ajax.php endpoints.

Recommended fix Moderate confidence

Latest version of Flex QR Code Generator (1.2.8 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Flex QR Code Generator' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/flex-qr-code-generator and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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