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-2026-0557: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in peterschulznl WP Data Access – No-Code App Builder with Tables, Forms, Charts & Maps

0
Medium
VulnerabilityCVE-2026-0557cvecve-2026-0557cwe-79
Published: Sat Feb 14 2026 (02/14/2026, 06:42:30 UTC)
Source: CVE Database V5
Vendor/Project: peterschulznl
Product: WP Data Access – No-Code App Builder with Tables, Forms, Charts & Maps

Description

The WP Data Access plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wpda_app' shortcode in all versions up to, and including, 5.5.63 due to insufficient input sanitization and output escaping on user supplied attributes. 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.

AI-Powered Analysis

AILast updated: 02/14/2026, 07:19:03 UTC

Technical Analysis

CVE-2026-0557 is a stored Cross-Site Scripting (XSS) vulnerability identified in the WP Data Access plugin for WordPress, a no-code app builder that facilitates creation of tables, forms, charts, and maps. The vulnerability exists in all versions up to and including 5.5.63, due to improper neutralization of user-supplied input in the 'wpda_app' shortcode. Specifically, the plugin fails to adequately sanitize and escape attributes provided by authenticated users with contributor-level or higher access. This flaw allows these users to inject arbitrary JavaScript code into pages, which is then stored and executed in the browser context of any user who visits the affected page. The attack vector is network-based, with low complexity, requiring only contributor-level privileges and no user interaction for the malicious script to execute. The vulnerability impacts confidentiality and integrity by enabling session hijacking, credential theft, or unauthorized actions performed in the context of the victim user. Availability is not directly impacted. The CVSS 3.1 score is 6.4, reflecting medium severity. No patches or known exploits are currently reported, but the vulnerability's presence in a widely used WordPress plugin makes it a notable risk. The scope is limited to WordPress sites using this plugin and having contributors with publishing rights. The vulnerability is classified under CWE-79, indicating improper input neutralization during web page generation.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to websites and web applications built on WordPress that utilize the WP Data Access plugin. Exploitation could lead to unauthorized script execution in users' browsers, resulting in session hijacking, theft of sensitive data such as cookies or credentials, and potential privilege escalation if administrative users are targeted. This could compromise the integrity of organizational websites, damage reputation, and lead to data breaches. Organizations with collaborative content creation workflows involving contributors are particularly vulnerable. The impact is heightened for sectors relying heavily on WordPress for customer engagement, such as e-commerce, media, education, and government portals. While availability is not directly affected, the indirect consequences of data compromise and trust erosion can be significant. Given the medium severity and ease of exploitation by authenticated users, organizations must assess their exposure and implement controls to prevent exploitation.

Mitigation Recommendations

1. Monitor for and apply official patches or updates from the WP Data Access plugin vendor as soon as they become available. 2. Restrict contributor-level permissions to trusted users only and review user roles regularly to minimize the risk of malicious input. 3. Implement strict input validation and output encoding at the application level, especially for user-supplied attributes in shortcodes or similar features. 4. Deploy a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting WordPress plugins. 5. Conduct regular security audits and penetration testing focusing on WordPress plugins and user-generated content. 6. Educate content contributors about security best practices and the risks of injecting untrusted content. 7. Consider disabling or limiting the use of the 'wpda_app' shortcode if it is not essential to reduce the attack surface. 8. Monitor logs for unusual activity or script injection attempts related to the plugin. 9. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 10. Backup WordPress sites regularly to enable quick restoration in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-01T21:38:05.369Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69901aebc9e1ff5ad8689310

Added to database: 2/14/2026, 6:49:15 AM

Last enriched: 2/14/2026, 7:19:03 AM

Last updated: 2/20/2026, 11:33:14 PM

Views: 25

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