There exists an unauthenticated BLE Interface in Sloan SmartFaucets including Optima EAF, Optima ETF/EBF, BASYS EFX, and Flushometers includ
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.54% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
There exists an unauthenticated BLE Interface in Sloan SmartFaucets including Optima EAF, Optima ETF/EBF, BASYS EFX, and Flushometers including SOLIS. The vulnerability allows for unauthenticated kinetic effects and information disclosure on the faucets. It is possible to use the Bluetooth Low Energy (BLE) connectivity to read and write to many BLE characteristics on the device. Some of these control the flow of water, the sensitivity of the sensors, and information about maintenance.
- Published
- Jun 30, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-306
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sloan | optima eaf-100 firmware | cpe:2.3:o:sloan:optima_eaf-100_firmware |
| sloan | optima eaf-100 | cpe:2.3:h:sloan:optima_eaf-100 |
| sloan | optima eaf-150 firmware | cpe:2.3:o:sloan:optima_eaf-150_firmware |
| sloan | optima eaf-150 | cpe:2.3:h:sloan:optima_eaf-150 |
| sloan | optima eaf-200 firmware | cpe:2.3:o:sloan:optima_eaf-200_firmware |
| sloan | optima eaf-200 | cpe:2.3:h:sloan:optima_eaf-200 |
| sloan | optima eaf-225 firmware | cpe:2.3:o:sloan:optima_eaf-225_firmware |
| sloan | optima eaf-225 | cpe:2.3:h:sloan:optima_eaf-225 |
| sloan | optima eaf-250 firmware | cpe:2.3:o:sloan:optima_eaf-250_firmware |
| sloan | optima eaf-250 | cpe:2.3:h:sloan:optima_eaf-250 |
| sloan | optima eaf-275 firmware | cpe:2.3:o:sloan:optima_eaf-275_firmware |
| sloan | optima eaf-275 | cpe:2.3:h:sloan:optima_eaf-275 |
and 130 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sloan basys efx-100 firmwareall versions
- sloan basys efx-150 firmwareall versions
- sloan basys efx-175 firmwareall versions
- sloan basys efx-177 firmwareall versions
- sloan basys efx-180 firmwareall versions
- sloan basys efx-200 firmwareall versions
- sloan basys efx-250 firmwareall versions
- sloan basys efx-275 firmwareall versions
- sloan basys efx-277 firmwareall versions
- sloan basys efx-280 firmwareall versions
- sloan basys efx-300 firmwareall versions
- sloan basys efx-350 firmwareall versions
- sloan basys efx-375 firmwareall versions
- sloan basys efx-377 firmwareall versions
- sloan basys efx-380 firmwareall versions
- sloan basys efx-600 firmwareall versions
- sloan basys efx-650 firmwareall versions
- sloan basys efx-675 firmwareall versions
- sloan basys efx-677 firmwareall versions
- sloan basys efx-680 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (tenable). Independent of NVD's CPE analysis and usually ahead of it.
n/a SLOAN
- All known versionsaffected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-primary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support teamapp.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) { app.post( "/maintenance/reset", requireSession, requireRole("admin"), resetDevice );}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.