mView <= 1.0.3 - Authenticated (Subscriber+) Arbitrary File Upload
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- mView 豆瓣电影
- Affected Version
<= 1.0.3- CVSS
- 8.8High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2026-115212
At a glance
CVE-2026-115212 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the mView 豆瓣电影 WordPress plugin, affecting versions <= 1.0.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2026, reported by Muni Nitish Kumar Yaddala.
Vulnerability Overview
The mView plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1.0.3. This is due to missing file type validation. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files on the affected site's server, which may make 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 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
Reaching this weakness in mView 豆瓣电影 <= 1.0.3 takes an account at Subscriber level or above. 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. No fixed build of this plugin is recorded for mView 豆瓣电影 yet, so installs running <= 1.0.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C