Multi Factor Authentication Bypass in various versions of Abacus ERP
A vulnerability within the authentication process of Abacus ERP allows a remote attacker to bypass the second authentication factor. This issue affects: Abacus ERP v2022 versions prior to R1 of 2022-01-15; v2021 versions prior to R4 of 2022-01-15; v2020 versions prior to R6 of 2022-01-15; v2019 versions later than R5 (service pack); v2018 versions later than R5 (service pack). This issue does not affect: Abacus ERP v2019 versions prior to R5 of 2020-03-15; v2018 versions prior to R7 of 2020-04-15; v2017 version and prior versions and prior versions.
- Published
- Apr 19, 2022
- Updated
- Jun 17, 2026
- EPSS
- 2.9% · 86th percentile
- CWE
- CWE-304
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.9%
CNA vs NVD score
- NVD
- 8.8
- CNA · NCSC.ch
- 8.1
- 0.7 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| abacus | abacus erp 2018 | cpe:2.3:a:abacus:abacus_erp_2018 |
| abacus | abacus erp 2019 | cpe:2.3:a:abacus:abacus_erp_2019 |
| abacus | abacus erp 2020 | cpe:2.3:a:abacus:abacus_erp_2020 |
| abacus | abacus erp 2021 | cpe:2.3:a:abacus:abacus_erp_2021 |
| abacus | abacus erp 2022 | cpe:2.3:a:abacus:abacus_erp_2022 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- abacus abacus erp 2018r7 and later
- abacus abacus erp 2019r5 and later
- abacus abacus erp 2020before r6
- abacus abacus erp 2021before r4
- abacus abacus erp 2022before r1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (NCSC.ch). Independent of NVD's CPE analysis and usually ahead of it.
Abacus Research AG Abacus ERP
- v2022 and later · before R1 of 2022-01-15affected
- v2021 and later · before R4 of 2022-01-15affected
- v2020 and later · before R6 of 2022-01-15affected
- R5 (service pack) and later · before v2019*affected
- R5 (service pack) and later · before v2018*affected
- v2017 and later · up to and including and prior versionsnot affected
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.
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
- 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-304 · Missing Critical Step in AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.