Quick Playground <= 1.3.1 - Missing Authorization to Unauthenticated Arbitrary File Upload
Strategic Overview
- Status
- Patched in 1.3.2
- Affected Plugin
- Quick Playground
- Affected Version
<= 1.3.1- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-1830
At a glance
CVE-2026-1830 is a critical-severity Missing Authorization vulnerability in the Quick Playground WordPress plugin, affecting versions <= 1.3.1. 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 1.3.2; sites on affected versions should update now. Disclosed April 2026, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
The Quick Playground plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.3.1. This is due to insufficient authorization checks on REST API endpoints that expose a sync code and allow arbitrary file uploads. This makes it possible for unauthenticated attackers to retrieve the sync code, upload PHP files with path traversal, and achieve remote code execution on the server.
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-862: Missing Authorization
Reaching this weakness in Quick Playground <= 1.3.1 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Quick Playground the fix is 1.3.2: builds <= 1.3.1 are affected, anything from 1.3.2 onward is not.
Remediation
Update to version 1.3.2, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Quick Playground 1.3.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Quick Playground
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C