CVE-2021-33605: Unauthorized property update in CheckboxGroup component in Vaadin 12-14 and 15-20
Noroxi assessment
Priority: Monitor (action score 17/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.66% (FIRST EPSS); higher than 52.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: com.vaadin:vaadin-checkbox-flow (Maven) 14.6.8, 20.0.6.
Low priority for now. Upgrade to com.vaadin:vaadin-checkbox-flow (Maven) 14.6.8, 20.0.6 or later.
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
Improper check in CheckboxGroup in com.vaadin:vaadin-checkbox-flow versions 1.2.0 prior to 2.0.0 (Vaadin 12.0.0 prior to 14.0.0), 2.0.0 prior to 3.0.0 (Vaadin 14.0.0 prior to 14.5.0), 3.0.0 through 4.0.1 (Vaadin 15.0.0 through 17.0.11), 14.5.0 through 14.6.7 (Vaadin 14.5.0 through 14.6.7), and 18.0.0 through 20.0.5 (Vaadin 18.0.0 through 20.0.5) allows attackers to modify the value of a disabled Checkbox inside enabled CheckboxGroup component via unspecified vectors.
- Published
- Aug 25, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-754
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 4.3
- CNA · Vaadin
- 4.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| vaadin | vaadin-checkbox-flow | cpe:2.3:a:vaadin:vaadin-checkbox-flow |
| vaadin | vaadin | cpe:2.3:a:vaadin:vaadin |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Vaadin). Independent of NVD's CPE analysis and usually ahead of it.
Vaadin Vaadin
- 12.0.0 and later · before unspecifiedaffected
- unspecified and later · before 14.0.0affected
- 14.0.0 and later · before unspecifiedaffected
- unspecified and later · before 14.5.0affected
- 15.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 17.0.11affected
- 14.5.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 14.6.7affected
- 18.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 20.0.5affected
Vaadin vaadin-checkbox-flow
- 1.2.0 and later · before unspecifiedaffected
- unspecified and later · before 2.0.0affected
- 2.0.0 and later · before unspecifiedaffected
- unspecified and later · before 3.0.0affected
- 3.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 4.0.1affected
- 14.5.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 14.6.7affected
- 18.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 20.0.5affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vaadin vaadin-checkbox-flow1.2.0 and later · before 2.0.0
- vaadin vaadin-checkbox-flow2.0.0 and later · before 3.0.0
- vaadin vaadin-checkbox-flow3.0.0 and later · before 4.0.1
- vaadin vaadin-checkbox-flow14.5.0 and later · before 14.6.7
- vaadin vaadin-checkbox-flow18.0.0 and later · before 20.0.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | com.vaadin:vaadin-checkbox-flow | from 12.0.0 · before 14.6.8 | 14.6.8 |
| Maven | com.vaadin:vaadin-checkbox-flow | from 15.0.0 · before 20.0.6 | 20.0.6 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:com.vaadin:vaadin-checkbox-flow | 14.6.8 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-checkbox-flow | 20.0.6 | Package registry (OSV) |
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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.