CVE-2022-4280 json
Dot Tech Smart Campus System findUser information disclosure
published 3y ago modified 4mo ago also EUVD-2022-51636
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as problematic, has been found in Dot Tech Smart Campus System. Affected by this issue is some unknown functionality of the file /services/Card/findUser. The manipulation leads to information disclosure. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-214778 is the identifier assigned to this vulnerability.
Is CVE-2022-4280 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/Peanut886/Vulnerability/blob/main/Information%20leakage%20vulnerability%20exists%20in%20findUser%2C%20a%20smart%20campus%20system%20developed%20by%20Dot%20Tech.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Dot Tech Smart Campus System
Classification
- Weakness
-
- CWE-266 Incorrect Privilege Assignment
References
-
github.com
/Peanut886/Vulnerability/blob/main/Information%20leakage%20vulnerability%20exists%20in%20findUser%2C%20a%20sma
exploit, third-party-advisory
-
vuldb.com
/?id.214778
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-4280
- NVD CVE-2022-4280
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.