Overview 27 matches · 8 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
27matches
8in Waratek scope29.6%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
2public PoC7.4%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
2
7.4%
No exploit published
6
22.2%
Outside Waratek scope
0
0.0%
Not applicable
19
70.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
27
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
7.4%
Proof of concept only
1
3.7%
Forecast only
0
0.0%
No public exploit
24
88.9%
split by
peak 12 / year
20071
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20080
20090
20101
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20110
20125
No exploit published4
Not applicable1
Medium5
not blocked5
No public exploit5
20130
20143
No exploit published1
Not applicable2
Medium3
not blocked3
No public exploit3
20150
20160
20170
20181
No exploit published1
Medium1
not blocked1
No public exploit1
20190
20200
20211
Not applicable1
Medium1
not blocked1
No public exploit1
20220
20232
Not applicable2
Medium2
not blocked2
No public exploit2
20241
Not applicable1
Medium1
not blocked1
No public exploit1
202512
Not applicable12
Medium12
not blocked12
Proof of concept only1
No public exploit11
2007200920112013201520172019202120232025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-66574 | Medium | 2025-12-04 | Not applicable | Proof of concept only | TranzAxis 3.2.41.10.26 allows authenticated users to inject cross-site scripting via the `Open Object in Tree` endpoint, allowing attackers to steal session cookies and potentially escalate privileges. |
| CVE-2025-8108 | Medium | 2025-11-11 | Not applicable | No public exploit | An ACAP configuration file has improper permissions and lacks input validation, which could potentially lead to privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-6779 | Medium | 2025-11-11 | Not applicable | No public exploit | An ACAP configuration file has improper permissions, which could allow command injection and potentially lead to privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-6298 | Medium | 2025-11-11 | Not applicable | No public exploit | ACAP applications can gain elevated privileges due to improper input validation, potentially leading to privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-5718 | Medium | 2025-11-11 | Not applicable | No public exploit | The ACAP Application framework could allow privilege escalation through a symlink attack. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-5454 | Medium | 2025-11-11 | Not applicable | No public exploit | An ACAP configuration file lacked sufficient input validation, which could allow a path traversal attack leading to potential privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-5452 | Medium | 2025-11-11 | Not applicable | No public exploit | A malicious ACAP application can gain access to admin-level service account credentials used by legitimate ACAP applications, leading to potential privilege escalation of the malicious ACAP application. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-4645 | Medium | 2025-11-11 | Not applicable | No public exploit | An ACAP configuration file lacked sufficient input validation, which could allow for arbitrary code execution. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-3892 | Medium | 2025-08-12 | Not applicable | No public exploit | ACAP applications can be executed with elevated privileges, potentially leading to privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-30027 | Medium | 2025-08-12 | Not applicable | No public exploit | An ACAP configuration file lacked sufficient input validation, which could allow for arbitrary code execution. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application. |
| CVE-2025-0361 | Medium | 2025-04-08 | Not applicable | No public exploit | During an annual penetration test conducted on behalf of Axis Communications, Truesec discovered a flaw in the VAPIX Device Configuration framework that allowed for unauthenticated username enumeration through the VAPIX Device Configuration SSH Management API. |
| CVE-2024-47261 | Medium | 2025-04-08 | Not applicable | No public exploit | 51l3nc3, a member of the AXIS OS Bug Bounty Program, has found that the VAPIX API uploadoverlayimage.cgi did not have sufficient input validation to allow an attacker to upload files to block access to create image overlays in the web interface of the Axis device. |
| CVE-2024-0055 | Medium | 2024-03-19 | Not applicable | No public exploit | Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX APIs mediaclip.cgi and playclip.cgi was vulnerable for file globbing which could lead to a resource exhaustion attack. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution. |
| CVE-2023-21405 | Medium | 2023-07-25 | Not applicable | No public exploit | Knud from Fraktal.fi has found a flaw in some Axis Network Door Controllers and Axis Network Intercoms when communicating over OSDP, highlighting that the OSDP message parser crashes the pacsiod process, causing a temporary unavailability of the door-controlling functionalities meaning that doors cannot be opened or closed. No sensitive or customer data can be extracted as the Axis device is not further compromised. Please refer to the Axis security advisory for more information, mitigation and affected products and software versions. |
| CVE-2023-21404 | Medium | 2023-05-08 | Not applicable | No public exploit | AXIS OS 11.0.X - 11.3.x use a static RSA key in legacy LUA-components to protect Axis-specific source code. The static RSA key is not used in any other secure communication nor can it be used to compromise the device or any customer data. |
| CVE-2021-31986 | Medium | 2021-10-05 | Not applicable | No public exploit | User controlled parameters related to SMTP notifications are not correctly validated. This can lead to a buffer overflow resulting in crashes and data leakage. |
| CVE-2018-8032 | Medium | 2018-08-02 | No exploit published | No public exploit | Apache Axis 1.x up to and including 1.4 is vulnerable to a cross-site scripting (XSS) attack in the default servlet/services. |
| CVE-2012-6107 | Medium | 2014-09-29 | Not applicable | No public exploit | Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. |
| CVE-2014-5639 | Medium | 2014-09-09 | Not applicable | No public exploit | The ADT Taxis (aka com.icabbi.adttaxisApp) application 6 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate. |
| CVE-2014-3596 | Medium | 2014-08-27 | No exploit published | No public exploit | The getCN function in Apache Axis 1.4 and earlier does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5784. |
| CVE-2012-5785 | Medium | 2012-11-04 | No exploit published | No public exploit | Apache Axis2/Java 1.6.2 and earlier does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. |
| CVE-2012-5784 | Medium | 2012-11-04 | No exploit published | No public exploit | Apache Axis 1.4 and earlier, as used in PayPal Payments Pro, PayPal Mass Pay, PayPal Transactional Information SOAP, the Java Message Service implementation in Apache ActiveMQ, and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. |
| CVE-2012-5351 | Medium | 2012-10-09 | No exploit published | No public exploit | Apache Axis2 allows remote attackers to forge messages and bypass authentication via a SAML assertion that lacks a Signature element, aka a "Signature exclusion attack," a different vulnerability than CVE-2012-4418. |
| CVE-2012-4418 | Medium | 2012-10-09 | No exploit published | No public exploit | Apache Axis2 allows remote attackers to forge messages and bypass authentication via an "XML Signature wrapping attack." |
| CVE-2012-0907 | Medium | 2012-01-20 | Not applicable | No public exploit | Directory traversal vulnerability in the web player in NeoAxis NeoAxis web player 1.4 and earlier allows user-assisted remote attackers to write arbitrary files via a .. (dot dot) in a filename in the neoaxis_web_application_win32.zip ZIP archive. |
| CVE-2010-2103 | Medium | 2010-05-27 | Mitigation candidate | Working exploit published | Cross-site scripting (XSS) vulnerability in axis2-admin/axis2-admin/engagingglobally in the administration console in Apache Axis2/Java 1.4.1, 1.5.1, and possibly other versions, as used in SAP Business Objects 12, 3com IMC, and possibly other products, allows remote attackers to inject arbitrary web script or HTML via the modules parameter. NOTE: some of these details are obtained from third party information. |
| CVE-2007-2353 | Medium | 2007-04-30 | Mitigation candidate | Working exploit published | Apache Axis 1.0 allows remote attackers to obtain sensitive information by requesting a non-existent WSDL file, which reveals the installation path in the resulting exception message. |