VulnerabilityPublished 10 Sep 2025Updated 8 Oct 2025

CVE-2025-10227: AxxonSoft AxxonOne C-Werk · Missing Encryption of Sensitive Data

Affects AxxonSoft AxxonOne C-WerkSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.07% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AxxonSoft AxxonOne C-Werk	Affected =0	Fixed in–

AI-suggested

Organizations should immediately assess their use of AxxonOne C-Werk and identify all instances running versions prior to 2.0.8. Until a patch is available, strict physical security controls must be enforced to prevent unauthorized access to exported archives and physical drives, including secure storage, access logging, and personnel vetting. Implement manual encryption of exported archive data using strong encryption tools before storage or transport. Regularly audit and monitor access to exported data and physical media. Establish policies for secure handling and disposal of storage devices containing sensitive data. Coordinate with AxxonSoft for timely updates and apply patches as soon as they are released. Additionally, consider network segmentation and limiting local access to systems managing sensitive archives to reduce insider threat risks. Training staff on the importance of physical security and data protection is also critical. Finally, review compliance with data protection regulations to ensure that current practices meet legal requirements for data confidentiality.

Description

Missing Encryption of Sensitive Data (CWE-311) in the Object Archive component in AxxonSoft Axxon One (C-Werk) before 2.0.8 on Windows and Linux allows a local attacker with access to exported storage or stolen physical drives to extract sensitive archive data in plaintext via lack of encryption at rest.

Impact

For European organizations, the exposure of sensitive archive data in plaintext poses significant confidentiality risks, especially for entities relying on AxxonOne C-Werk for video surveillance and security management. Such data may include sensitive video footage, personally identifiable information, or security event logs, which if disclosed, could lead to privacy violations, regulatory non-compliance (e.g., GDPR), and reputational damage. Critical infrastructure operators, government agencies, and private enterprises using this software are particularly vulnerable if physical security controls are insufficient. The risk is exacerbated in environments where exported storage media are transported or stored offsite without encryption. Although the vulnerability does not allow remote exploitation, insider threats or theft of physical drives could result in data breaches. The medium severity rating reflects the limited attack vector but significant confidentiality impact. European organizations must consider the regulatory implications of unencrypted sensitive data and potential legal liabilities.

CWE-311Missing Encryption of Sensitive Data (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not encrypt sensitive or critical information before storage or transmission.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.
Architecture and Design
Ensure that encryption is properly integrated into the system design, including but not necessarily limited to: Encryption that is needed to store or transmit private data of the users of the system; Encryption that is needed to protect the system itself from unauthorized disclosure or tampering
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
User Privacy Protection (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V6.1.3 (opens in a new tab)
V6.1.2 (opens in a new tab)
V6.1.1 (opens in a new tab)
Attack patterns
Sniffing Attacks (opens in a new tab)
Sniffing Network Traffic (opens in a new tab)
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

axxonsoft.com/legal/axxonsoft-vulnerability-disclosure-policy/security-advisories (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Oct 2025, 12:14 UTC

WeaknessesCWE-311

Technical details

References

Community reviews

Related threats