CVE-2025-13852
BaseFortify
Publication date: 2026-01-09
Last updated on: 2026-01-09
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| debtcom | business_in_a_box | to 4.1.0 (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?
CVE-2025-13852 is a Stored Cross-Site Scripting (XSS) vulnerability in the Debt.com Business in a Box WordPress plugin (up to version 4.1.0). It occurs via the 'configuration' parameter of the lead_form shortcode due to insufficient input sanitization and output escaping. Authenticated users with Contributor-level access or higher can inject malicious scripts into pages, which execute when other users view those pages. The vulnerability arises from improper handling of dynamic parameters used in generating the HTML form in the plugin's bib_form.php file, allowing arbitrary web script injection. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow attackers with Contributor-level access or higher to inject malicious scripts into the website's pages. These scripts execute in the context of users who visit the infected pages, potentially leading to theft of user credentials, session hijacking, defacement, or distribution of malware. It compromises the integrity and security of the website and its users by enabling persistent cross-site scripting attacks.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting WordPress installations for the presence of the Debt.com Business in a Box plugin version 4.1.0 or earlier. Specifically, look for the usage of the 'lead_form' shortcode with the 'configuration' parameter that may be exploited. Detection can involve reviewing the plugin files, especially 'bib_form.php', for unsanitized input handling. Additionally, monitoring HTTP requests for suspicious payloads in the 'configuration' parameter or injected scripts in pages generated by the plugin can help identify exploitation attempts. Since the vulnerability involves stored cross-site scripting, scanning the database or pages served by the plugin for injected scripts is useful. Commands to assist detection might include: 1) Using WP-CLI to check plugin version: `wp plugin list --format=json | jq '.[] | select(.name=="debtcom-business-in-a-box")'` 2) Searching plugin files for vulnerable code patterns: `grep -r --include='bib_form.php' 'configuration' wp-content/plugins/debtcom-business-in-a-box/` 3) Using curl or wget to fetch pages using the lead_form shortcode and inspecting responses for injected scripts. 4) Scanning the database for suspicious script tags in post content or plugin options related to the plugin. However, no specific detection commands are provided in the resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Updating the Debt.com Business in a Box WordPress plugin to a version later than 4.1.0 where the vulnerability is fixed, if available. 2) If an update is not available, temporarily disabling or removing the plugin to prevent exploitation. 3) Restricting Contributor-level and higher user permissions to trusted users only, as the vulnerability requires authenticated users with at least Contributor access. 4) Implementing Web Application Firewall (WAF) rules to block malicious payloads targeting the 'configuration' parameter of the lead_form shortcode. 5) Reviewing and sanitizing any stored data that may have been injected with malicious scripts. 6) Monitoring logs and site content for signs of exploitation. Since the vulnerability arises from insufficient input sanitization and output escaping in the plugin's form generation, applying patches or updates that fix these issues is critical. [1, 2]