Demi - One Click Demo Import, Backup & Site Migration <= 0.0.6 - Unauthenticated Sensitive Data Exposure
Strategic Overview
- Status
- Patched in 0.0.7
- Affected Plugin
- Demi – One Click Demo Import, Backup & Site Migration
- Affected Version
<= 0.0.6- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-14333
At a glance
CVE-2026-14333 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Demi WordPress plugin, affecting versions <= 0.0.6. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 0.0.7; sites on affected versions should update now. Disclosed July 2026, reported by Pavan N.
Vulnerability Overview
The Demi - One Click Demo Import, Backup & Site Migration plugin for WordPress is vulnerable to Information Exposure in versions up to, and including, 0.0.6. This is due to backup files stored in a publicly accessible directory with predictable, time-based filenames and an index.php that silenced rather than blocked directory browsing. This makes it possible for unauthenticated attackers to download backup archive files directly by guessing predictable URLs in the public backup directory.
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.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Demi <= 0.0.6 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Demi the fix is 0.0.7: builds <= 0.0.6 are affected, anything from 0.0.7 onward is not.
Remediation
Update to version 0.0.7, 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: Demi 0.0.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Demi – One Click Demo Import, Backup & Site Migration
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C