Horizon Alert
Summary of the vulnerability and why it matters
A critical vulnerability has been identified in a popular WordPress plugin that allows for website translation. This issue could enable unauthorized individuals to access administrator account credentials, potentially leading to full control of your WordPress sites. The primary concern is to confirm if this plugin is in use and if the specific conditions for exploitation are met.
- Sensitive data exposure in translation plugin.
- Potential for administrator account takeover.
- Confirm relevance and exposure on our sites.
Attack Path
How an attacker could exploit the issue
An attacker can exploit this vulnerability by targeting a WordPress site using the TranslatePress plugin. If automatic string saving is enabled and an administrator's profile is set to a published secondary language, the system inadvertently stores sensitive password reset information as a translatable string. An unauthenticated attacker can then use a specific AJAX action to retrieve this stored information, gaining access to a raw administrator password-reset URL that includes the reset key and login parameters. This allows the attacker to take over an administrator account.
- No authentication required to access.
- AJAX action triggers sensitive data exposure.
- Enables full administrator account takeover.
Live Threat
Current exploitation, exposure, and threat context
Under specific conditions, such as when automatic string saving is enabled and an administrator's profile is set to a published secondary language, this vulnerability could expose administrator password-reset URLs, including the reset key and login parameters. This exposure could enable an attacker to take over an administrator account.
- Administrator account credentials.
- Stored password reset URLs.
- Full administrator account takeover.
Operational Fix
Recommended remediation, mitigation, and detection steps
Real-world ownership of this critical vulnerability likely falls to the application or platform teams managing the WordPress instances, potentially with vendor-management teams coordinating with the plugin provider. The immediate practical first step is to identify all WordPress sites using this plugin, confirm their exposure (especially if automatic string saving is enabled and secondary languages are published), and determine the business criticality of each instance to prioritize remediation efforts.
- Application owners should own this issue.
- Verify affected plugin and settings first.
- Plan remediation based on exposure and criticality.