001 Prime Strategy Translate Accelerator <= 1.1.1 - Missing Authorization
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- 001 Prime Strategy Translate Accelerator
- Affected Version
<= 1.1.1- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a medium-severity Missing Authorization vulnerability in the 001 Prime Strategy Translate Accelerator WordPress plugin, affecting versions <= 1.1.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2022.
Vulnerability Overview
The 001 Prime Strategy Translate Accelerator plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the update_psta_settings() function called via a plugins_loaded action in versions up to, and including, 1.1.1. This makes it possible for unauthenticated attackers to delete the plugin's cache.
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.
CWE-862: Missing Authorization
001 Prime Strategy Translate Accelerator <= 1.1.1 carries this weakness at update_psta_settings(), and reaching it takes a caller who can reach the endpoint. 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 001 Prime Strategy Translate Accelerator yet, so installs running <= 1.1.1 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?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. 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