Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-4590 Overview
The Daisycon prijsvergelijkers plugin for WordPress contains a stored Cross-Site Scripting (XSS) vulnerability in the daisycon_uitvaart shortcode. The flaw affects all versions up to and including 4.9.0. Insufficient input sanitization and output escaping on user supplied shortcode attributes allow script injection. Authenticated users with contributor-level access or above can inject arbitrary web scripts into pages. Those scripts execute whenever any user visits the affected page. The weakness is tracked under CWE-79.
Critical Impact
Contributor-level accounts can plant persistent JavaScript payloads that execute in the context of site visitors and administrators, enabling session theft, forced actions, and content manipulation.
Affected Products
- Daisycon prijsvergelijkers plugin for WordPress — all versions through 4.9.0
- WordPress sites exposing the daisycon_uitvaart shortcode to contributor-level editors
- Any WordPress environment running the vulnerable plugin build published on the Daisycon WordPress Plugin page
Discovery Timeline
- 2025-05-31 - CVE-2025-4590 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-4590
Vulnerability Analysis
The vulnerability is a stored XSS flaw rooted in how the plugin processes the daisycon_uitvaart shortcode. When a contributor inserts the shortcode into a post or page, the plugin accepts attributes supplied by the user. The plugin fails to sanitize those attributes on input and does not escape them on output. The attacker-controlled values are rendered directly into the HTML response delivered to visitors. The injected payload persists in the database because WordPress stores the post content, so every subsequent view of the page triggers execution of the attacker's JavaScript in the visitor's browser.
Root Cause
The root cause is the absence of two WordPress-standard security routines. The plugin does not call sanitization helpers such as sanitize_text_field() or attribute validators on the shortcode arguments. It also does not call output-escaping functions like esc_attr() or esc_html() when writing the attributes back into the rendered HTML. This matches the classic CWE-79 pattern of improper neutralization of input during web page generation.
Attack Vector
An authenticated attacker with contributor or higher privileges creates or edits a post containing the daisycon_uitvaart shortcode. The attacker supplies a crafted attribute value containing HTML and JavaScript. When an editor previews, an administrator reviews, or a public visitor loads the page, the browser parses the injected markup and executes the payload. Typical outcomes include administrator session hijacking, forced plugin or user changes through CSRF chains, and client-side redirection to attacker-controlled infrastructure.
Technical details and the fix are documented in the WordPress Plugin Changeset and the Wordfence Vulnerability Report.
Detection Methods for CVE-2025-4590
Indicators of Compromise
- Posts or pages containing a daisycon_uitvaart shortcode with attribute values that include <script>, onerror=, onload=, javascript: or encoded variants.
- Unexpected outbound requests from visitor browsers to third-party domains originating on pages that render the vulnerable shortcode.
- New or modified posts authored by contributor-level accounts shortly before suspicious client-side behavior appears.
Detection Strategies
- Scan wp_posts.post_content for the daisycon_uitvaart shortcode and inspect each attribute for HTML tags, event handlers, or URL schemes.
- Enforce a Content Security Policy (CSP) in report-only mode to surface inline script executions and unexpected script sources from WordPress pages.
- Review WordPress audit logs for contributor-created or edited content that correlates with alerts from browser-side telemetry.
Monitoring Recommendations
- Monitor WordPress role assignments and watch for unexpected promotions to the contributor role or higher.
- Alert on edits to pages that embed Daisycon shortcodes, especially when authored by low-privilege accounts.
- Track browser error reports and CSP violation reports for script-src and inline-script events tied to public URLs.
How to Mitigate CVE-2025-4590
Immediate Actions Required
- Update the Daisycon prijsvergelijkers plugin to a version released after 4.9.0 that includes the fix referenced in the plugin changeset.
- Audit all existing posts and pages that use the daisycon_uitvaart shortcode and remove any attribute values containing HTML or script content.
- Rotate credentials and session tokens for administrator accounts that may have viewed compromised pages.
Patch Information
The vendor published a corrective changeset tracked in the WordPress plugin repository. Review the WordPress Plugin Changeset and install the latest release from the Daisycon WordPress Plugin page. Validate the installed version is greater than 4.9.0 after upgrade.
Workarounds
- Deactivate the Daisycon prijsvergelijkers plugin until the patched release is deployed.
- Restrict the contributor role or require editor-level approval before publishing content containing shortcodes.
- Deploy a web application firewall rule that blocks shortcode attributes containing <, >, or javascript: patterns targeting WordPress endpoints.
# Configuration example: identify posts containing the vulnerable shortcode
wp db query "SELECT ID, post_title, post_author FROM wp_posts \
WHERE post_content LIKE '%[daisycon_uitvaart%' \
AND post_status IN ('publish','draft','pending');"
# Temporarily deactivate the plugin until patched
wp plugin deactivate daisycon
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

