| Plugin Name | Prisna GWT – Google Website Translator |
|---|---|
| Type of Vulnerability | Cross-Site Scripting (XSS) |
| CVE Number | CVE-2024-12680 |
| Urgency | Low |
| CVE Publish Date | 2026-01-30 |
| Source URL | CVE-2024-12680 |
CVE-2024-12680: Critical Admin Stored XSS Vulnerability in Prisna GWT – Google Website Translator Plugin (≤ 1.4.13) — Essential Guidance for WordPress Site Administrators
Author: Managed-WP Security Experts
Date: 2026-01-30
Tags: WordPress, XSS, WAF, Prisna GWT, Security, CVE-2024-12680
Executive Summary: A stored Cross‑Site Scripting vulnerability (CVE‑2024‑12680) has been identified in versions prior to 1.4.14 of the Prisna GWT – Google Website Translator WordPress plugin. This flaw requires administrator-level credentials to exploit and involves administrator interaction, but it enables malicious JavaScript execution within the trusted admin context. Immediate plugin update to version 1.4.14, thorough database inspections, and application of recommended mitigations—including Managed-WP firewall protections and administrative hardening—are strongly advised to prevent compromise.
Incident Overview
On January 30, 2026, a security advisory was issued for the “Prisna GWT – Google Website Translator” WordPress plugin, highlighting a stored Cross-Site Scripting (XSS) vulnerability tracked as CVE-2024-12680. This vulnerability affects all plugin versions older than 1.4.14.
Unlike typical XSS attacks targeting public users, this is an “Admin Stored XSS”—meaning that malicious payloads inserted via plugin settings can execute in the browser session of authenticated administrators who view specific plugin settings pages or UI elements. Despite being rated low urgency due to privilege and user interaction requirements, the risk for persistent administrative account compromise remains significant.
Understanding “Admin Stored XSS”
A stored XSS occurs when untrusted input is saved on the server and later rendered unsafely in a user’s browser, enabling JavaScript execution. Here, the vulnerability manifests inside admin panel interfaces:
- Administrator-level users can inadvertently trigger malicious payloads embedded in plugin data.
- The JavaScript runs with full administrator privileges in the browser context.
- This execution could permit attackers to alter site configurations, insert backdoors, hijack sessions, or escalate further attacks.
This flaw is specifically caused by inadequate sanitization of admin input fields before rendering in the plugin’s settings pages.
Affected Versions and Scope
- Plugin: Prisna GWT – Google Website Translator
- Vulnerable Versions: All prior to 1.4.14
- Patched Version: 1.4.14
- CVE Identifier: CVE-2024-12680
- Required Privileges: Administrator
- User Interaction: Required (Admin must interact with crafted content)
- Security Category: OWASP A3 – Injection (XSS)
The Criticality of Addressing Admin-Level XSS
While exploitation demands administrative credentials and interaction, this vulnerability amplifies risks because attackers can:
- Leverage phishing or social engineering to convince an admin to trigger the malicious payload.
- Achieve persistent code injection that modifies sensitive site configurations.
- Hijack admin sessions by stealing authentication tokens or cookies.
- Establish persistent backdoors enabling further lateral movement post-exploit.
Given the high value of administrator access, response and remediation must be swift.
Exploit Overview (Conceptual)
- An attacker with admin access inputs malicious JavaScript code into plugin settings fields.
- This payload is saved by the plugin and is rendered without proper sanitizing whenever admins view those settings pages.
- When an admin visits an affected page, the script executes in their browser session.
- The attacker gains the ability to perform privileged operations through the compromised session.
Immediate Recommended Actions
- Update Plugin: Immediately upgrade Prisna GWT to version 1.4.14 or later on all environments.
- Temporarily Disable If Immediate Update Isn’t Feasible: Deactivate the plugin until patched.
- Audit Administration Accounts: Enforce password resets, invalidate active sessions, and enable two-factor authentication (2FA) for all admins.
- Search For Suspicious Script Content: Examine your database entries (particularly wp_options and meta tables) using targeted queries for malicious script tags or event handlers.
- Implement Firewall Protections: Use Managed-WP’s WAF (or similar) to block requests containing suspicious JavaScript payloads targeting admin endpoints.
- Clean Injected Payloads: Carefully remove any discovered injections, restoring from clean backups if needed.
Detection Strategies
Look out for these potential signs of exploitation:
- Unexpected new or altered admin accounts.
- Irregular changes in plugin files or settings.
- Database entries containing script tags or suspicious JavaScript attributes.
- Unusual or unauthorized outbound traffic patterns.
- Admin logins from unknown IP addresses or at unusual times.
Sample detection queries can examine the wp_options and metadata tables for script tags and event attributes — always execute on a staging or backup database copy.
Safe Remediation Workflow
- Isolate: Place your site into maintenance mode, disable the vulnerable plugin.
- Backup: Take a complete backup, ensuring forensic integrity.
- Remove Malicious Content: Use secure, PHP-serialization-aware search and replace tools to sanitize the database.
- Reinstall Patched Plugin: Use fresh packages from trusted sources after cleanup.
- Harden Admin Credentials: Reset passwords, enable 2FA, and restrict admin roles to minimum necessary users.
- Monitor: Maintain vigilant post-cleanup monitoring for anomalies in admin behavior or traffic.
Managed-WP WAF Temporary Virtual Patch Recommendations
While patch deployment is the definitive fix, Managed-WP’s Web Application Firewall provides immediate, virtual patching mitigation by filtering malicious output:
- Block suspicious POST requests: Deny admin POST bodies containing “<script”, “onerror=”, “onload=”, “javascript:” or encoded variants.
- Sanitize Admin Output: Optionally strip script tags and inline event handlers from admin responses (requires careful tuning).
- Protect plugin AJAX endpoints: Filter malicious payloads targeting admin-ajax.php relevant actions.
- Strictly rate limit critical admin actions: Enforce re-authentication or second factor for sensitive changes.
- Restrict Admin IP Access: Use IP allowlists or VPN access for /wp-admin/ where possible.
- Implement Content Security Policies: Enforce restrictive CSP headers on admin pages to block inline scripts.
Important: Deploy firewall rules initially in monitor mode to fine-tune and prevent false positives before enforcement.
Administrator Hardening Best Practices
- Grant Administrator privileges only to essential personnel.
- Maintain separate accounts for admin and regular content management.
- Enforce strong password policies combined with 2FA.
- Regularly audit and remove unnecessary or outdated plugins.
- Centralize update management with prompt application of security patches.
- Implement activity logging and file integrity monitoring.
- Maintain tested backups with at least one offline copy.
Post-Incident Forensic Actions
- Preserve all server and firewall logs, plus backups.
- Engage experienced security teams for incident investigation.
- Reinstall WordPress core, themes, and plugins from trusted sources.
- Rotate API keys, OAuth tokens, and other secrets.
- Notify stakeholders and comply with applicable reporting requirements.
Frequently Asked Questions
Q: Can attackers exploit this remotely without admin access?
A: No. Exploitation requires administrator credentials and interaction with crafted content. It is not exploitable anonymously or remotely without credentials.
Q: Can non-admin users exploit this?
A: No. The vulnerability is specific to admin interface data rendering. That said, attackers might combine this with escalation vulnerabilities elsewhere.
Q: Is a WAF alone enough protection?
A: While a WAF provides crucial immediate mitigation through virtual patching, timely plugin update remains essential. Firewall rules are a stopgap, not a cure.
Q: Should I uninstall the plugin?
A: If you don’t require its translation features, uninstalling reduces attack surface. Otherwise, promptly update and harden your admin environment.
How Managed-WP Protects Your WordPress Site
At Managed-WP, we adopt a layered security approach combining:
- Proactive WAF virtual patching to block exploitation attempts.
- Continuous vulnerability scanning and malware detection.
- Expert remediation support and personalized onboarding.
- Best practice enforcement including admin hardening and role-based traffic filtering.
For CVE-2024-12680, we deploy specialized WAF signatures to detect and mitigate malicious admin-side XSS payloads and guide customers in rapid patch application and cleanup.
Start Securing Your WordPress Site Today with Managed-WP’s Free Plan
Want immediate protection while you update? Our Managed-WP Free Plan delivers essential firewall services (WAF), unlimited bandwidth, malware scanning, and mitigation of top OWASP risks. Block attacks like stored XSS effortlessly and free of charge.
Sign up here for basic managed protection:
https://my.wp-firewall.com/buy/wp-firewall-free-plan/
Need automated malware removal, virtual patching at scale, and advanced admin controls? Upgrade to Managed-WP Standard or Pro plans designed for enterprise-grade security.
Comprehensive Action Checklist
- Update the Prisna GWT plugin to 1.4.14 or later.
- If update is delayed, deactivate the plugin and enable Managed-WP temporary WAF rules.
- Audit and clean your database for malicious script injections.
- Reset all admin passwords and enable 2FA across admin accounts.
- Monitor logs for suspicious activity indicating compromise.
- Use staging environments to validate updates and mitigations before production deployment.
Our Managed-WP security team is ready to assist with tailored virtual patching, vulnerability scanning, and step-by-step cleanup plans to ensure your WordPress site’s integrity.
Stay secure,
The Managed-WP Security Team
Take Proactive Action — Secure Your Site with Managed-WP
Don’t risk your business or reputation due to overlooked plugin flaws or weak permissions. Managed-WP provides robust Web Application Firewall (WAF) protection, tailored vulnerability response, and hands-on remediation for WordPress security that goes far beyond standard hosting services.
Exclusive Offer for Blog Readers: Access our MWPv1r1 protection plan—industry-grade security starting from just USD 20/month.
- Automated virtual patching and advanced role-based traffic filtering
- Personalized onboarding and step-by-step site security checklist
- Real-time monitoring, incident alerts, and priority remediation support
- Actionable best-practice guides for secrets management and role hardening
Get Started Easily — Secure Your Site for USD 20/month:
Protect My Site with Managed-WP MWPv1r1 Plan
Why trust Managed-WP?
- Immediate coverage against newly discovered plugin and theme vulnerabilities
- Custom WAF rules and instant virtual patching for high-risk scenarios
- Concierge onboarding, expert remediation, and best-practice advice whenever you need it
Don’t wait for the next security breach. Safeguard your WordPress site and reputation with Managed-WP—the choice for businesses serious about security.
Click above to start your protection today (MWPv1r1 plan, USD 20/month).


















