Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-19632 – Unauthenticated Account Takeover via Password-Reset URL Disclosure – TranslatePress

Be the first to know when new zero-days emerge:

Summary

CVE-2026-19632 is a critical unauthenticated account takeover vulnerability in the TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress, caused by a weak password recovery mechanism (CWE-640). The flaw allows an unauthenticated attacker to recover the plaintext administrator password-reset key through a plugin AJAX action, leading to full administrator account compromise. It affects TranslatePress versions up to and including 3.3.1 and carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: the plugin’s trp_get_translations_regular AJAX action, which is registered for both authenticated and unauthenticated ("nopriv") requests, returns translated string data without adequately restricting access to sensitive content.
  • Trigger conditions: exploitation requires TranslatePress’s automatic string saving feature to be enabled (the default configuration) and the site administrator’s account locale to be set to a secondary, published language on the site.
  • Attack vector: network-based, unauthenticated, no user interaction required, low attack complexity — an attacker can query the AJAX endpoint directly to retrieve translation strings that include the administrator’s raw password-reset URL and plaintext reset key.
  • Impact: full compromise of the confidentiality, integrity, and availability of the affected site, since the disclosed reset key can be used to reset the administrator password and take over the account, and from there the entire WordPress site.

Affected software

  • TranslatePress – Translate Multilingual sites with AI Translation (developed by cozmoslabs), versions 0 through 3.3.1 (inclusive).

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade TranslatePress to version 3.3.2 or later, the first release published after the affected 3.3.1 line closed by this advisory. Always confirm against the currently installed version and the vendor’s official changelog before and after patching.
  • If immediate patching is not possible: disable the "automatic add strings for translation" / automatic string saving feature, and ensure the administrator account’s profile locale is not set to a secondary/published language on the site, as both conditions are required for exploitation.
  • General hardening: restrict or monitor direct requests to WordPress admin-ajax.php actions where feasible, enforce two-factor authentication for administrator accounts, and review site user activity and password-reset logs for signs of compromise following disclosure.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/translatepress-multilingual/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge