OMGF Pro <= 5.2.6 - Unauthenticated Arbitrary File Upload via @import URL Reflection
Strategic Overview
- Status
- Patched in 5.2.7
- Affected Plugin
- OMGF Pro
- Affected Version
<= 5.2.6- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2026-57700
At a glance
CVE-2026-57700 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the OMGF Pro WordPress plugin, affecting versions <= 5.2.6. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.2.7; sites on affected versions should update now. Disclosed June 2026, reported by Nguyen Ngoc Duc (duc193).
Vulnerability Overview
The OMGF Pro plugin for WordPress is vulnerable to Unrestricted File Type Upload in all versions up to, and including, 5.2.6. This is due to the ExternalStylesheets::optimize() method extracting attacker-controlled @import URLs from the rendered HTML, fetching their contents via wp_remote_get(), and writing those contents to disk via file_put_contents() at a path derived directly from the attacker-controlled URL host/path — with no file-extension allowlist, MIME check, or capability/nonce gate on the omgf_optimize and omgf_pro_auto_config GET parameters that trigger the pipeline. This makes it possible for unauthenticated attackers to upload arbitrary files (including PHP) into the uploads directory on the affected site's server which makes remote code execution possible.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
OMGF Pro <= 5.2.6 carries this weakness at optimize(), and reaching it takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For OMGF Pro the fix is 5.2.7: builds <= 5.2.6 are affected, anything from 5.2.7 onward is not.
Remediation
Update to version 5.2.7, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: OMGF Pro 5.2.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C