Floristpress For Woo Customize Your Ecommerce Store For Your Florist
CVE-2026-1986
|
EUVD-2026-16084
MEDIUM
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS 3.1 score of 6.1 (Medium) reflects moderate risk with the vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N indicating network accessibility, low attack complexity, no privilege requirements, but mandatory user interaction. The scope change (S:C) is notable as it affects resources beyond the vulnerable component. However, this vulnerability carries real-world risk for eCommerce sites: florist shops using this plugin expose customers to session hijacking, credential theft, and malware distribution through reflected XSS. The requirement for user interaction (clicking a malicious link) reduces the attack surface compared to stored XSS but does not eliminate risk-phishing campaigns targeting florist shop customers are entirely plausible. Without confirmed EPSS score, KEV listing, or public exploit code in the provided data, the practical exploitability appears moderate; however, the simplicity of XSS exploitation and the plugin's WordPress ecosystem visibility suggest opportunistic attackers would quickly weaponize this if not patched. WordPress plugin users are typically slower to update than enterprise software consumers, extending the exploitation window. |
| Exploit ScenarioDerived | An attacker constructs a URL such as |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
A Reflected Cross-Site Scripting (XSS) vulnerability exists in FloristPress for Woo (BakkBone) plugin versions up to 7.8.2, where the 'noresults' parameter is insufficiently sanitized and escaped, allowing unauthenticated attackers to inject arbitrary JavaScript. An attacker can craft a malicious URL and trick users into clicking it, resulting in script execution within the victim's browser session with access to sensitive data and session tokens. The vulnerability requires user interaction (UI:R) but has a network attack vector with low complexity, and while no KEV or confirmed active exploitation data is available in the provided intelligence, Wordfence has documented the issue with references to vulnerable code locations.
RemediationAI
Upgrade FloristPress for Woo to a patched version beyond 7.8.2 immediately; check the vendor's WordPress plugin page or BakkBone's official website for the latest available version, with reference to the Wordfence threat intelligence page at https://www.wordfence.com/threat-intel/vulnerabilities/id/ea3b6fa6-1b58-40c2-8ec2-8a9211069f11?source=cve for patch details and version numbers. The underlying fix requires implementing proper input validation and output encoding for the 'noresults' parameter using WordPress sanitization functions (such as sanitize_text_field()) on input and escaping functions (such as esc_attr() or wp_kses_post()) on output. Until the plugin is patched, implement a Web Application Firewall (WAF) rule to block requests with suspicious script-like payloads in the 'noresults' parameter, and educate staff and customers to avoid clicking untrusted links to your website; additionally, monitor for signs of XSS exploitation (unusual JavaScript execution, session anomalies) in web server and WordPress security logs.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is rooted in CWE-79 (Improper Neutralization of Input During Web Page Generation, also known as Cross-Site Scripting), a foundational web application security flaw. The affected product is FloristPress for Woo (CPE:2.3:a:bakkbone:floristpress_for_woo_-_customize_your_ecommerce_store_for_your_florist), a WordPress plugin that customizes eCommerce stores for florists. The specific vulnerability resides in the AJAX handler at src/core/ajax.php (line 1583 as referenced in the WordPress plugin repository), where user-supplied input from the 'noresults' parameter is reflected back into the HTTP response without proper sanitization using WordPress security functions like sanitize_text_field() or escaping output using esc_attr() or esc_html(). This failure allows an attacker-controlled payload to be interpreted as executable code by the browser DOM or JavaScript engines.
Know when Floristpress For Woo Customize Your Ecommerce Store For Your Florist gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
The FloristPress for Woo - Customize your eCommerce store for your Florist plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'noresults' parameter in all versions up to, and including, 7.8.2 due to insufficient input sanitization and output escaping on the user supplied 'noresults' parameter. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
Executive ViewAI
Organizations using all should be aware of moderate risk from CVE-2026-1986, a cross-site scripting vulnerability rated CVSS 6.1. Attackers could inject scripts to steal sessions or perform actions as authenticated users. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: implement CSP headers, enable HttpOnly cookies, deploy WAF XSS rules.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
GHSA-g85c-6q3h-m8pv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB