FloristPress for Woo – Customize your eCommerce store for your Florist
bakkbone-florist-companion · plugin
Known security vulnerabilities for FloristPress for Woo – Customize your eCommerce store for your Florist. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
2 exploitable without logging in · latest Mar 26, 2026
Before you install
Use with care
- 2 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 7.8.4 · last updated May 8, 2026 · 10+ installs
wordpress.org status checked on Oct 21, 2026
Vulnerabilities
- High 7.1
CVE-2024-54347unauthenticated · needs a click≤ 7.2.0
WordPress FloristPress plugin <= 7.2.0 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 6.1
CVE-2026-1986unauthenticated · needs a click≤ 7.8.2
FloristPress for Woo <= 7.8.2 - Reflected Cross-Site Scripting via 'noresults' Parameter
- Medium 5.4
CVE-2024-53798login required≤ 7.3.0
WordPress FloristPress plugin <= 7.3.0 - Nonce Leakage to Broken Access Control vulnerability
- Medium 4.3
CVE-2024-53799login required≤ 7.3.0
WordPress FloristPress plugin <= 7.3.0 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).