Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14937: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in shabti Frontend Admin by DynamiApps

0
High
VulnerabilityCVE-2025-14937cvecve-2025-14937cwe-79
Published: Fri Jan 09 2026 (01/09/2026, 07:22:10 UTC)
Source: CVE Database V5
Vendor/Project: shabti
Product: Frontend Admin by DynamiApps

Description

The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'acff' parameter in the 'frontend_admin/forms/update_field' AJAX action in all versions up to, and including, 3.28.23 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.

AI-Powered Analysis

AILast updated: 01/09/2026, 07:56:34 UTC

Technical Analysis

CVE-2025-14937 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Frontend Admin by DynamiApps plugin for WordPress, affecting all versions up to and including 3.28.23. The vulnerability exists due to improper neutralization of input during web page generation, specifically insufficient sanitization and escaping of the 'acff' parameter in the 'frontend_admin/forms/update_field' AJAX action. This flaw allows unauthenticated attackers to inject arbitrary JavaScript code that is stored on the server and executed in the context of any user who views the affected page, potentially compromising user sessions, stealing cookies, or performing actions on behalf of users. The vulnerability is notable because it requires no authentication or user interaction to exploit, increasing its risk profile. The CVSS v3.1 score of 7.2 reflects a high severity, with network attack vector, low attack complexity, no privileges required, no user interaction, and a scope change indicating that the vulnerability affects resources beyond the initially vulnerable component. Although no public exploits have been reported yet, the widespread use of WordPress and the plugin increases the likelihood of future exploitation. The vulnerability is categorized under CWE-79, which covers improper neutralization of input leading to XSS. The lack of a patch link suggests that a fix may not yet be publicly available, emphasizing the need for vigilance and interim mitigations.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on WordPress sites with the affected plugin installed. Successful exploitation can lead to session hijacking, unauthorized actions performed on behalf of users, defacement of websites, and potential distribution of malware through injected scripts. This can damage organizational reputation, lead to data breaches involving user credentials or personal data, and disrupt business operations. Public-facing websites, customer portals, and administrative interfaces are particularly at risk. Given the unauthenticated nature of the exploit, attackers can target any vulnerable site without needing credentials, increasing the attack surface. The scope change in the CVSS vector indicates that the vulnerability can affect components beyond the plugin itself, potentially impacting other integrated systems. European organizations subject to GDPR may face regulatory consequences if user data is compromised. The absence of known exploits currently provides a window for proactive defense, but the risk of exploitation will increase once exploit code becomes available.

Mitigation Recommendations

Immediate mitigation should focus on monitoring and restricting access to the vulnerable AJAX endpoint, possibly by implementing web application firewall (WAF) rules that detect and block suspicious payloads targeting the 'acff' parameter. Organizations should subscribe to vendor updates and apply patches promptly once released. In the absence of an official patch, manual code review and hardening can be performed by sanitizing and encoding inputs and outputs related to the vulnerable parameter. Implementing Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Regular security scanning and penetration testing should be conducted to detect exploitation attempts. Additionally, organizations should educate users and administrators about the risks of XSS and encourage the use of multi-factor authentication to reduce the impact of session hijacking. Backup and incident response plans should be updated to address potential exploitation scenarios. Finally, limiting the exposure of administrative interfaces and enforcing least privilege principles can reduce the attack surface.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-18T21:15:38.790Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6960b130ecefc3cd7c0f7d15

Added to database: 1/9/2026, 7:41:36 AM

Last enriched: 1/9/2026, 7:56:34 AM

Last updated: 1/9/2026, 11:09:46 PM

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats