Export to Text <= 2.4 - Unauthenticated Post Export
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Export to Text
- Affected Version
<= 2.4- CVSS
- 7.5High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the Export to Text WordPress plugin, affecting versions <= 2.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2022.
Vulnerability Overview
The Export to Text plugin for WordPress is vulnerable to unauthenticated post exporting due to a missing capability check on the sre2t_ajax() AJAX function and the export_to_text_download() function hooked via wp_loaded in versions up to, and including 2.4. This makes it possible for attackers to retrieve potentially sensitive information within posts.
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-862: Missing Authorization
Export to Text <= 2.4 carries this weakness at sre2t_ajax(), and reaching it 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. No fixed build of this plugin is recorded for Export to Text yet, so installs running <= 2.4 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?
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C