Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 5 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,764exploited flaws on CISA’s list
35added in the last 30 days
456new WordPress flaws this week
390,714entries in the database

59 results · page 1 of 2

  • Oct 21, 2026Translate WordPress with Weglot 2.0: Does not escape the URLs it re-inserts into a pageCVE-2026-88784 · WordPress plugins & themes · reported by WPScanHigh 7.5

    The Translate WordPress with Weglot 2.0 WordPress plugin before 6.4.3 does not escape the URLs it re-inserts into a page when rewriting links for a translated language, and reverses the encoding that was applied to them beforehand, allowing unauthenticated users to store a payload which executes in the browser of anyone viewing the page in a translated language.

    Product
    Translate WordPress with Weglot 2.0
    Fixed in
    6.4.3
    What to do
    Update Translate WordPress with Weglot 2.0 to 6.4.3 or newer.
  • Oct 16, 2026TranslatePress – Translate Multilingual sites with AI Translation: Stored Cross-Site ScriptingCVE-2026-107768 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 3.3.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the target site to allow unmoderated comment submission on at least one post and to have a secondary language configured — both conditions reflect TranslatePress's primary use case.

    Product
    TranslatePress – Translate Multilingual sites with AI Translation
    Affected
    up to 3.3.7
    What to do
    Affects up to 3.3.7. Update TranslatePress – Translate Multilingual sites with AI Translation to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 8, 2026GPTranslate: Does not properly restrict who can store translationsCVE-2026-103309 · WordPress plugins & themes · reported by WPScanHigh 7.5

    The GPTranslate WordPress plugin before 2.34.14 does not properly restrict who can store translations, and does not escape them when outputting them in translated pages, allowing unauthenticated users to perform Stored Cross-Site Scripting attacks when server-side translations are enabled.

    Product
    GPTranslate
    Fixed in
    2.34.14
    What to do
    Update GPTranslate to 2.34.14 or newer.
  • Oct 4, 2026TranslatePress: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2026-103062 · WordPress plugins & themes · reported by PatchstackHigh 7.1

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Cozmoslabs TranslatePress translatepress-multilingual allows Stored XSS.This issue affects TranslatePress: from n/a through 3.3.6.

    Product
    TranslatePress
    Affected
    up to 3.3.6
    What to do
    Affects up to 3.3.6. Update TranslatePress to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 3, 2026Loco Translate: Does not sanitise and escape some bundle configuration values before outputting them back in an admin pageCVE-2026-94239 · WordPress plugins & themes · reported by WPScanMedium 6.8

    The Loco Translate WordPress plugin before 2.8.9 does not sanitise and escape some bundle configuration values before outputting them back in an admin page, allowing users with the translator capability and above to perform Stored Cross-Site Scripting attacks against high privilege users such as administrators.

    Product
    Loco Translate
    Fixed in
    2.8.9
    What to do
    Update Loco Translate to 2.8.9 or newer.
  • Oct 3, 2026Loco Translate: Does not restrictCVE-2026-94238 · WordPress plugins & themes · reported by WPScanMedium 6.8

    The Loco Translate WordPress plugin before 2.8.9 does not restrict which file paths its translation file routes will read, allowing users granted the Loco Translate WordPress plugin before 2.8.9's translator capability to retrieve the contents of files of certain types from anywhere on the server, including outside the web root.

    Product
    Loco Translate
    Fixed in
    2.8.9
    What to do
    Update Loco Translate to 2.8.9 or newer.
  • Sep 23, 2026GTranslate: Does not remove shortcodes from the content of outgoing emails before expanding them whichCVE-2026-86604 · WordPress plugins & themes · reported by WPScanMedium 4.8

    The GTranslate WordPress plugin before 5.0.1 does not remove shortcodes from the content of outgoing emails before expanding them which, in a non-default configuration, allows unauthenticated users to have arbitrary shortcodes registered on the site executed server side.

    Product
    GTranslate
    Fixed in
    5.0.1
    What to do
    Update GTranslate to 5.0.1 or newer.
  • Sep 22, 2026TranslatePress – Translate Multilingual sites with AI Translation: Stored Cross-Site ScriptingCVE-2026-89412 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Translation Memory Suggestion Panel (v-html on suggestion.original) in all versions up to, and including, 3.3.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Unauthenticated attackers can seed the translation dictionary's original column with executable HTML because the front-end rendering pipeline decodes entity-encoded payloads via html_entity_decode() before persistence, and the original column is deliberately exempt from kses filtering — meaning no save-time sanitizer neutralizes the stored payload before it is later rendered in an administrator's session.

    Product
    TranslatePress – Translate Multilingual sites with AI Translation
    Affected
    up to 3.3.5
    What to do
    Affects up to 3.3.5. Update TranslatePress – Translate Multilingual sites with AI Translation to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 18, 2026GPTranslate – Multilingual AI Translation Agent for WordPress: Translate Your Site with AI: Sensitive Information ExposureCVE-2026-89278 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The GPTranslate – Multilingual AI Translation Agent for WordPress: Translate Your Site with AI plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.34.6 via the enqueue_frontend_scripts. This makes it possible for unauthenticated attackers to extract the plaintext third-party AI provider API key (OpenAI, DeepL, xAI/Grok, Gemini, Claude, or Google Cloud Translation) — a credential granting billed account access — by fetching any public page and applying the inverse transformation bundled in the plugin's own public JavaScript asset. This exposure affects the default configuration (gpt-3.5-turbo in client mode) and all supported non-DeepSeek providers; only deepseek-* models and gpt-* models configured in server-proxy mode correctly suppress key emission.

    Product
    GPTranslate – Multilingual AI Translation Agent for WordPress: Translate Your Site with AI
    Affected
    up to 2.34.6
    What to do
    Affects up to 2.34.6. Update GPTranslate – Multilingual AI Translation Agent for WordPress: Translate Your Site with AI to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 11, 2026Translate WordPress with GTranslate: Does not validate one of its settings before the bundled front-end scripts build markup from itCVE-2025-15695 · WordPress plugins & themes · reported by WPScanLow 3.5

    The Translate WordPress with GTranslate WordPress plugin before 3.0.10 does not validate one of its settings before the bundled front-end scripts build markup from it, allowing users with a role as high as administrator to store JavaScript that runs in the session of any visitor to the site.

    Product
    Translate WordPress with GTranslate
    Fixed in
    3.0.10
    What to do
    Update Translate WordPress with GTranslate to 3.0.10 or newer.
  • Aug 28, 2026TranslatePress – Translate Multilingual sites with AI Translation: Stored Cross-Site ScriptingCVE-2026-76053 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Noise-Key Injection into HTML Parser in all versions up to, and including, 3.3.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation is possible because WordPress's comment KSES allowlist permits the payload structure — an anchor tag with href and title attributes alongside a code tag — causing the malicious comment to be stored verbatim in the database, where it is later processed by the vulnerable parser during page translation.

    Product
    TranslatePress – Translate Multilingual sites with AI Translation
    Affected
    up to 3.3.3
    What to do
    Affects up to 3.3.3. Update TranslatePress – Translate Multilingual sites with AI Translation to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 26, 2026TranslatePress – Translate Multilingual sites with AI Translation: Sensitive Information ExposureCVE-2026-19632 · WordPress plugins & themes · reported by WordfenceCritical 9.8

    The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.3.1 via the 'trp_get_translations_regular' AJAX action. This makes it possible for unauthenticated attackers to extract the raw administrator password-reset URL — including the plaintext reset key and login parameters stored in the translation dictionary table — enabling full administrator account takeover. This vulnerability is only exploitable when automatic string saving is enabled (the default setting) and the target administrator's profile locale is set to a published secondary language, as these conditions cause the password-reset URL to be persisted as a translatable string in the secondary-language dictionary table.

    Product
    TranslatePress – Translate Multilingual sites with AI Translation
    Affected
    up to 3.3.1
    What to do
    Affects up to 3.3.1. Update TranslatePress – Translate Multilingual sites with AI Translation to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 25, 2026TranslatePress – Translate Multilingual sites with AI Translation: Stored Cross-Site ScriptingCVE-2026-18512 · WordPress plugins & themes · reported by WordfenceMedium 6.4

    The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Approved Comment Body Rendered in Translation Editor Strings Dropdown in all versions up to, and including, 3.2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Product
    TranslatePress – Translate Multilingual sites with AI Translation
    Affected
    up to 3.2.6
    What to do
    Affects up to 3.2.6. Update TranslatePress – Translate Multilingual sites with AI Translation to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 24, 2026Unauthenticated Privilege Escalation in TranslatePress <= 3.3.2 versions.CVE-2026-78267 · WordPress plugins & themes · reported by PatchstackCritical 9.8

    Unauthenticated Privilege Escalation in TranslatePress <= 3.3.2 versions.

    Affected
    up to 3.3.2
    What to do
    Affects up to 3.3.2. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 20, 2026Unauthenticated Cross Site Scripting (XSS) in TranslatePress <= 3.3.2 versions.CVE-2026-66582 · WordPress plugins & themes · reported by PatchstackHigh 7.1

    Unauthenticated Cross Site Scripting (XSS) in TranslatePress <= 3.3.2 versions.

    Affected
    up to 3.3.2
    What to do
    Affects up to 3.3.2. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 19, 2026TranslatePress – Translate Multilingual sites with AI Translation: Unauthenticated Stored Cross-Site ScriptingCVE-2026-75981 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to unauthenticated Stored Cross-Site Scripting in versions up to and including 3.2.5. The special gettext markers '#!trpst#' and '#!trpen#' are unconditionally rewritten to '<' and '>' by translate_page() in includes/class-translation-render.php (lines 538-539). Because those markers are plain text with no HTML-special characters, an unauthenticated attacker can embed them in a comment; the markers survive wp_kses, and when the post is viewed in a secondary language the substitution turns the attacker's '#!trpst#img ... #!trpen#' into a real <img> tag. remove_tags_from_output() only strips <script>/<style>, so an <img onerror=...> executes in the visitor's browser.

    Product
    TranslatePress – Translate Multilingual sites with AI Translation
    Affected
    up to 3.2.5
    What to do
    Affects up to 3.2.5. Update TranslatePress – Translate Multilingual sites with AI Translation to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 16, 2026Loco Translate: Stored Cross-Site ScriptingCVE-2026-15066 · WordPress plugins & themes · reported by WordfenceMedium 6.4

    The Loco Translate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via PO File Extracted Comments in all versions up to, and including, 2.8.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with translator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Product
    Loco Translate
    Affected
    up to 2.8.7
    What to do
    Affects up to 2.8.7. Update Loco Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 6, 2026TranslatePress – Translate Multilingual sites with AI Translation: Stored Cross-Site ScriptingCVE-2026-18510 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content (URL-encoded gettext markers) in all versions up to, and including, 3.2.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Comment moderation may delay exploitation for first-time commenters, but does not prevent it, as the payload uses only WordPress-permitted tags and attributes with percent-encoded characters that pass wp_kses URL validation unmodified.

    Product
    TranslatePress – Translate Multilingual sites with AI Translation
    Affected
    up to 3.2.6
    What to do
    Affects up to 3.2.6. Update TranslatePress – Translate Multilingual sites with AI Translation to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 5, 2026Translate Multilingual sites – TranslatePress: Reflected Cross-Site ScriptingCVE-2026-17505 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The Translate Multilingual sites – TranslatePress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in versions up to, and including, 3.2.5. This is due to the translate_page() function unconditionally replacing the plugin's internal #!trpst# and #!trpen# marker tokens with literal angle brackets across the entire HTML page output after WordPress has already sanitized and escaped user input — allowing the attacker to bypass WordPress's normal HTML escaping by using these tokens, which are not HTML special characters, in the search query. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a specially crafted link.

    Product
    Translate Multilingual sites – TranslatePress
    Affected
    up to 3.2.5
    What to do
    Affects up to 3.2.5. Update Translate Multilingual sites – TranslatePress to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 16, 2026Loco Translate: Cross-Site Request ForgeryCVE-2026-15005 · WordPress plugins & themes · reported by WordfenceHigh 8.8

    The Loco Translate plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8.5. This is due to missing or incorrect nonce validation on the execTemplate function. This makes it possible for unauthenticated attackers to execute arbitrary PHP code on the server by supplying a php://filter stream wrapper URI as the 'template' parameter, which bypasses path validation and is passed directly to the include sink in execTemplate() via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Loco Translate
    Affected
    up to 2.8.5
    What to do
    Affects up to 2.8.5. Update Loco Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 15, 2026Unauthenticated SQL Injection in GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites <= 2.32.6 versions.CVE-2026-49776 · WordPress plugins & themes · reported by PatchstackCritical 9.3

    Unauthenticated SQL Injection in GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites <= 2.32.6 versions.

    Affected
    up to 2.32.6
    What to do
    Affects up to 2.32.6. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 13, 2026GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites: Stored Cross-Site ScriptingCVE-2026-9109 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REST API Translation Storage in all versions up to, and including, 2.31 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The deterministically derived API key (sha256 of the site URL) is printed in the HTML source of every page via the JavaScript variable gptApiKey, meaning any unauthenticated visitor can retrieve the key and submit malicious translation payloads to the /wp-json/gptranslate/v1/request endpoint without any additional precondition.

    Product
    GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites
    Affected
    up to 2.31
    What to do
    Affects up to 2.31. Update GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 4, 2026Loco Translate: Path TraversalCVE-2026-1921 · WordPress plugins & themes · reported by WordfenceMedium 4.9

    The Loco Translate plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 2.8.2 via the `fsReference` AJAX route. This is due to the `findSourceFile()` method normalizing user-supplied `ref` paths containing `../` directory traversal sequences without validating that the resolved path remains within the intended bundle or content directory. This makes it possible for authenticated attackers, with Translator-level access and above (custom `loco_admin` capability required, granted to the `translator` role and administrators by default), to read arbitrary `.php`, `.js`, `.json`, and `.twig` files from the server filesystem outside the intended translation directory. Files named wp-config.php are excluded.

    Product
    Loco Translate
    Affected
    up to 2.8.2
    What to do
    Affects up to 2.8.2. Update Loco Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Mar 31, 2026Loco Translate: Reflected Cross-Site ScriptingCVE-2026-4146 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The Loco Translate plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘update_href’ parameter in all versions up to, and including, 2.8.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

    Product
    Loco Translate
    Affected
    up to 2.8.2
    What to do
    Affects up to 2.8.2. Update Loco Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Nov 6, 2025TranslatePress: Deserialization of Untrusted DataCVE-2025-58592 · WordPress plugins & themes · reported by PatchstackHigh 8.1

    Deserialization of Untrusted Data vulnerability in Cozmoslabs TranslatePress translatepress-multilingual allows Object Injection.This issue affects TranslatePress: from n/a through <= 2.10.2.

    Product
    TranslatePress
    Affected
    up to 2.10.2
    What to do
    Affects up to 2.10.2. Update TranslatePress to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 30, 2025Translate WordPress and go Multilingual – Weglot: Unauthorized loss of dataCVE-2025-10008 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The Translate WordPress and go Multilingual – Weglot plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'clean_options' function in all versions up to, and including, 5.1. This makes it possible for unauthenticated attackers to delete limited transients that contain cached plugin options.

    Product
    Translate WordPress and go Multilingual – Weglot
    Affected
    up to 5.1
    What to do
    Affects up to 5.1. Update Translate WordPress and go Multilingual – Weglot to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 11, 2025My WP Translate: Unauthorized modification of data that can lead to privilege escalationCVE-2025-8425 · WordPress plugins & themes · reported by WordfenceHigh 8.8

    The My WP Translate plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the ajax_import_strings() function in all versions up to, and including, 1.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

    Product
    My WP Translate
    Affected
    up to 1.1
    What to do
    Affects up to 1.1. Update My WP Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 11, 2025My WP Translate: Unauthorized modification of dataCVE-2025-8423 · WordPress plugins & themes · reported by WordfenceMedium 5.4

    The My WP Translate plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the mtswpt_remove_plugin() and ajax_update_export_code() functions in all versions up to, and including, 1.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read and delete arbitrary WordPress options which can cause a denial of service.

    Product
    My WP Translate
    Affected
    up to 1.1
    What to do
    Affects up to 1.1. Update My WP Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 5, 2025Translate This gTranslate Shortcode: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2025-58880 · WordPress plugins & themes · reported by PatchstackMedium 6.5

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in reubenthiessen Translate This gTranslate Shortcode translate-this-google-translate-web-element-shortcode allows Stored XSS.This issue affects Translate This gTranslate Shortcode: from n/a through <= 1.0.

    Product
    Translate This gTranslate Shortcode
    Affected
    up to 1.0
    What to do
    Affects up to 1.0. Update Translate This gTranslate Shortcode to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 16, 2025Translate This gTranslate Shortcode: Stored Cross-Site ScriptingCVE-2025-8719 · WordPress plugins & themes · reported by WordfenceMedium 6.4

    The Translate This gTranslate Shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘base_lang’ parameter in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Product
    Translate This gTranslate Shortcode
    Affected
    up to 1.0
    What to do
    Affects up to 1.0. Update Translate This gTranslate Shortcode to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Mar 27, 2025TranslatePress: Deserialization of Untrusted DataCVE-2025-30773 · WordPress plugins & themes · reported by PatchstackHigh 7.2

    Deserialization of Untrusted Data vulnerability in Cozmoslabs TranslatePress translatepress-multilingual allows Object Injection.This issue affects TranslatePress: from n/a through <= 2.9.6.

    Product
    TranslatePress
    Affected
    up to 2.9.6
    What to do
    Affects up to 2.9.6. Update TranslatePress to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Feb 13, 2025TinyMCE Advanced qTranslate fix editor problems: Cross-Site Request Forgery (CSRF)CVE-2025-26582 · WordPress plugins & themes · reported by PatchstackHigh 7.1

    Cross-Site Request Forgery (CSRF) vulnerability in Blackbam TinyMCE Advanced qTranslate fix editor problems tinymce-advanced-qtranslate-fix-editor-problems allows Stored XSS.This issue affects TinyMCE Advanced qTranslate fix editor problems: from n/a through <= 1.0.0.

    Product
    TinyMCE Advanced qTranslate fix editor problems
    Affected
    up to 1.0.0
    What to do
    Affects up to 1.0.0. Update TinyMCE Advanced qTranslate fix editor problems to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jan 2, 2025Loco Translate: Cross-Site Request Forgery (CSRF)CVE-2024-37236 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Cross-Site Request Forgery (CSRF) vulnerability in Tim W Loco Translate loco-translate allows Cross Site Request Forgery.This issue affects Loco Translate: from n/a through <= 2.6.9.

    Product
    Loco Translate
    Affected
    up to 2.6.9
    What to do
    Affects up to 2.6.9. Update Loco Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Dec 9, 2024qTranslate X Cleanup and WPML Import: Missing AuthorizationCVE-2023-29431 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Missing Authorization vulnerability in OntheGoSystems qTranslate X Cleanup and WPML Import allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects qTranslate X Cleanup and WPML Import: from n/a through 3.0.1.

    Product
    qTranslate X Cleanup and WPML Import
    Affected
    up to 3.0.1
    What to do
    Affects up to 3.0.1. Update qTranslate X Cleanup and WPML Import to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Nov 1, 2024Language Translate Widget for WordPress – ConveyThis: Missing AuthorizationCVE-2024-38792 · WordPress plugins & themes · reported by PatchstackMedium 5.3

    Missing Authorization vulnerability in ConveyThis Translate Team Language Translate Widget for WordPress – ConveyThis allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Language Translate Widget for WordPress – ConveyThis: from n/a through 234.

    Product
    Language Translate Widget for WordPress – ConveyThis
    Affected
    up to 234
    What to do
    Affects up to 234. Update Language Translate Widget for WordPress – ConveyThis to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 31, 2024WPGlobus Translate Options: Cross-Site Request ForgeryCVE-2024-9434 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The WPGlobus Translate Options plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.0. This is due to missing or incorrect nonce validation on the on__translate_options_page() function. This makes it possible for unauthenticated attackers to inject malicious web scripts and update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    WPGlobus Translate Options
    Affected
    up to 2.2.0
    What to do
    Affects up to 2.2.0. Update WPGlobus Translate Options to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 11, 2024WP Translate: Missing AuthorizationCVE-2024-35663 · WordPress plugins & themes · reported by PatchstackMedium 5.4

    Missing Authorization vulnerability in HahnCreativeGroup WP Translate.This issue affects WP Translate: from n/a through 5.3.0.

    Product
    WP Translate
    Affected
    up to 5.3.0
    What to do
    Affects up to 5.3.0. Update WP Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 22, 2024Automatic Translator with Google Translate: Stored Cross-Site ScriptingCVE-2024-0632 · WordPress plugins & themes · reported by WordfenceMedium 4.4

    The Automatic Translator with Google Translate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the custom font setting in all versions up to, and including, 1.5.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

    Product
    Automatic Translator with Google Translate
    Affected
    up to 1.5.4
    What to do
    Affects up to 1.5.4. Update Automatic Translator with Google Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2024TranslatePress: Cross-Site Request Forgery (CSRF)CVE-2024-34827 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Cross-Site Request Forgery (CSRF) vulnerability in Cozmoslabs, Razvan Mocanu, Madalin Ungureanu, Cristophor Hurduban TranslatePress.This issue affects TranslatePress: from n/a through 2.7.5.

    Product
    TranslatePress
    Affected
    up to 2.7.5
    What to do
    Affects up to 2.7.5. Update TranslatePress to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 10, 2024Language Translate Widget for WordPress – ConveyThis: Stored Cross-Site ScriptingCVE-2023-6811 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The Language Translate Widget for WordPress – ConveyThis plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'api_key’ parameter in all versions up to, and including, 223 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Product
    Language Translate Widget for WordPress – ConveyThis
    Affected
    up to 223
    What to do
    Affects up to 223. Update Language Translate Widget for WordPress – ConveyThis to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Mar 20, 2024Translate WordPress and go Multilingual – Weglot: Stored Cross-Site ScriptingCVE-2024-2124 · WordPress plugins & themes · reported by WordfenceMedium 6.4

    The Translate WordPress and go Multilingual – Weglot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's widget/block in all versions up to, and including, 4.2.5 due to insufficient input sanitization and output escaping on user supplied attributes such as 'className'. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Product
    Translate WordPress and go Multilingual – Weglot
    Affected
    up to 4.2.5
    What to do
    Affects up to 4.2.5. Update Translate WordPress and go Multilingual – Weglot to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Dec 20, 2023Bravo Translate: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVE-2023-49161 · WordPress plugins & themes · reported by PatchstackHigh 7.6

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Guelben Bravo Translate.This issue affects Bravo Translate: from n/a through 1.2.

    Product
    Bravo Translate
    Affected
    up to 1.2
    What to do
    Affects up to 1.2. Update Bravo Translate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 25, 2023Translate WordPress with GTranslate: Does not sanitise and escape some of its settingsCVE-2023-4502 · WordPress plugins & themes · reported by WPScanMedium 4.8

    The Translate WordPress with GTranslate WordPress plugin before 3.0.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). This vulnerability affects multiple parameters.

    Product
    Translate WordPress with GTranslate
    Fixed in
    3.0.4
    What to do
    Update Translate WordPress with GTranslate to 3.0.4 or newer.
  • Jul 12, 2023Qtranslate Slug: Cross-Site Request ForgeryCVE-2021-4410 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Qtranslate Slug plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.18. This is due to missing or incorrect nonce validation on the save_postdata() function. This makes it possible for unauthenticated attackers to save post data via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Qtranslate Slug
    Affected
    up to 1.1.18
    What to do
    Affects up to 1.1.18. Update Qtranslate Slug to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Mar 6, 2023A vulnerability was found in Qtranslate Slug Plugin up to 1.1.16 on WordPress.CVE-2015-10092 · WordPress plugins & themes · reported by VulDBLow 3.5

    A vulnerability was found in Qtranslate Slug Plugin up to 1.1.16 on WordPress. It has been classified as problematic. Affected is the function add_slug_meta_box of the file includes/class-qtranslate-slug.php. The manipulation leads to cross site scripting. It is possible to launch the attack remotely. Upgrading to version 1.1.17 is able to address this issue. The name of the patch is 74b3932696f9868e14563e51b7d0bb68c53bf5e4. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-222324.

    Product
    Qtranslate Slug
    Affected
    up to 1.1.16
    What to do
    Affects up to 1.1.16. Update Qtranslate Slug to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 19, 2022Translate Multilingual sites: Is vulnerable to an authenticated SQL injectionCVE-2022-3141 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The Translate Multilingual sites WordPress plugin before 2.3.3 is vulnerable to an authenticated SQL injection. By adding a new language (via the settings page) containing specific special characters, the backticks in the SQL query can be surpassed and a time-based blind payload can be injected.

    Product
    Translate Multilingual sites
    Fixed in
    2.3.3
    What to do
    Update Translate Multilingual sites to 2.3.3 or newer.
  • Apr 18, 2022Loco Translate: Does not properly remove inline events from elements in the source translation strings before outputting them in the editor in the plugin admin panelCVE-2022-0765 · WordPress plugins & themes · reported by WPScanMedium 5.4

    The Loco Translate WordPress plugin before 2.6.1 does not properly remove inline events from elements in the source translation strings before outputting them in the editor in the plugin admin panel, allowing any user with access to the plugin (Translator and Administrator by default) to add arbitrary javascript payloads to the source strings leading to a stored cross-site scripting (XSS) vulnerability.

    Product
    Loco Translate
    Fixed in
    2.6.1
    What to do
    Update Loco Translate to 2.6.1 or newer.
  • Mar 28, 2022Translate WordPress with GTranslate: Does not have CSRF check in some filesCVE-2022-0770 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The Translate WordPress with GTranslate WordPress plugin before 2.9.9 does not have CSRF check in some files, and write debug data such as user's cookies in a publicly accessible file if a specific parameter is used when requesting them. Combining those two issues, an attacker could gain access to a logged in admin cookies by making them open a malicious link or page

    Product
    Translate WordPress with GTranslate
    Fixed in
    2.9.9
    What to do
    Update Translate WordPress with GTranslate to 2.9.9 or newer.
  • Feb 7, 2022Translate WordPress with GTranslate: Does not sanitise and escape the body parameter in the url_addon/gtranslate-emailCVE-2021-25103 · WordPress plugins & themes · reported by WPScanMedium 4.7

    The Translate WordPress with GTranslate WordPress plugin before 2.9.7 does not sanitise and escape the body parameter in the url_addon/gtranslate-email.php file before outputting it back in the page, leading to a Reflected Cross-Site Scripting issue. Note: exploitation of the issue requires knowledge of the NONCE_SALT and NONCE_KEY

    Product
    Translate WordPress with GTranslate
    Fixed in
    2.9.7
    What to do
    Update Translate WordPress with GTranslate to 2.9.7 or newer.
  • Nov 8, 2021Loco Translate: Mishandles data inputsCVE-2021-24721 · WordPress plugins & themes · reported by WPScanMedium 6.5

    The Loco Translate WordPress plugin before 2.5.4 mishandles data inputs which get saved to a file, which can be renamed to an extension ending in .php, resulting in authenticated "translator" users being able to inject PHP code into files ending with .php in web accessible locations.

    Product
    Loco Translate
    Fixed in
    2.5.4
    What to do
    Update Loco Translate to 2.5.4 or newer.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.