Apexsoftcell develops a narrow set of back-office and geolocation products where identified vulnerabilities center on authentication and data-exposure issues, including authentication bypass, excessive-attempt inadequacy, and improper integrity checking. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Apexsoftcell over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-47088CRITICAL This vulnerability exists in Apex Softcell LD Geo due to missing restrictions for excessive failed authentication attempts on its API based login. A remote attacker could exploit t | Sep 19, 2024 | 9.8 | 27 | NO | NO |
CVE-2024-47085MEDIUM This vulnerability exists in Apex Softcell LD DP Back Office due to improper validation of certain parameters (cCdslClicentcode and cLdClientCode) in the API endpoint. An authentic | Sep 19, 2024 | 6.5 | 20 | NO | NO |
CVE-2024-47089MEDIUM This vulnerability exists in the Apex Softcell LD Geo due to improper validation of the transaction token ID in the API endpoint. An authenticated remote attacker could exploit thi | Sep 19, 2024 | 6.5 | 19 | NO | NO |
CVE-2024-47087MEDIUM This vulnerability exists in Apex Softcell LD Geo due to improper validation of the certain parameters (Client ID, DPID or BOID) in the API endpoint. An authenticated remote attack | Sep 19, 2024 | 6.5 | 19 | NO | NO |
CVE-2024-47086MEDIUM This vulnerability exists in Apex Softcell LD DP Back Office due to improper implementation of OTP validation mechanism in certain API endpoints. An authenticated remote attacker c | Sep 19, 2024 | 6.5 | 19 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Apexsoftcell.
Media articles that mention a CVE ID that affects a product developed by Apexsoftcell — matched by CVE ID, not by vendor name.