CVE-2025-15440
Stored XSS in iONE360 WordPress Plugin Contact Form Parameters
Publication date: 2026-02-11
Last updated on: 2026-02-11
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ione360 | configurator | to 2.0.57 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2025-15440 is a Stored Cross-Site Scripting (XSS) vulnerability in the iONE360 configurator plugin for WordPress, affecting all versions up to and including 2.0.57. It arises because the plugin does not properly sanitize or escape user input submitted via its contact form parameters.'}, {'type': 'paragraph', 'content': "This vulnerability allows unauthenticated attackers to inject arbitrary web scripts into pages that are stored in the plugin's database and later executed whenever a user accesses those injected pages, particularly in the WordPress admin interface where the data is displayed."}] [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts in the context of your WordPress admin panel or other users who view the injected content. This can lead to unauthorized actions such as stealing session cookies, performing actions on behalf of users, or defacing the admin interface.
Because the vulnerability is exploitable without authentication, attackers do not need to log in to inject malicious scripts, increasing the risk of compromise.
The plugin stores user-submitted data including contact details and product configurations, and displays this data without proper sanitization, which can be exploited to inject harmful scripts.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by inspecting the WordPress installation for the presence of the iONE360 configurator plugin, specifically versions up to and including 2.0.57.'}, {'type': 'paragraph', 'content': 'Detection involves checking the database table named `{wpdb_prefix}configurator_contact_form` for stored user-submitted data that may contain malicious scripts.'}, {'type': 'paragraph', 'content': 'Additionally, reviewing the WordPress admin interface where the contact form submissions are displayed can reveal if any stored Cross-Site Scripting payloads are present due to insufficient sanitization.'}, {'type': 'paragraph', 'content': 'Suggested commands to detect the plugin version and presence of the vulnerable table include:'}, {'type': 'list_item', 'content': 'Use WP-CLI to check the plugin version: `wp plugin list --fields=name,version | grep ione360-configurator`'}, {'type': 'list_item', 'content': "Use a MySQL command to check for the existence of the contact form table: `SHOW TABLES LIKE '%configurator_contact_form%';`"}, {'type': 'list_item', 'content': "Query the table for suspicious or script-containing entries: `SELECT contact_full_name, contact_email, contact_message FROM {wpdb_prefix}configurator_contact_form WHERE contact_message LIKE '%<script>%';`"}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the iONE360 configurator plugin to a version later than 2.0.57 where the vulnerability is fixed.
If an update is not immediately available, disable or deactivate the plugin to prevent exploitation.
Additionally, restrict access to the WordPress admin interface to trusted users only, as the vulnerability involves stored scripts executing in the admin panel.
Review and sanitize existing entries in the `{wpdb_prefix}configurator_contact_form` database table to remove any malicious scripts.
Implement Web Application Firewall (WAF) rules to block common XSS payloads targeting the contact form parameters.