dbcve.org
Axxon OneApplication · Axxonsoft

CVE-2025-10223

HIGH · 8.1 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to after 2.0.2 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insufficient Session Expiration (CWE-613) in the Web Admin Panel in AxxonSoft Axxon One (C-Werk) prior to 2.0.3 on Windows allows a local or remote authenticated attacker to retain access with removed privileges via continued use of an unexpired session token until natural expiration.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AxxonSoft Axxon One Web Admin Panel prior to version 2.0.3 on Windows does not properly invalidate session tokens when user privileges are removed or user roles are changed. An authenticated attacker whose privileges have been revoked can continue using the existing session token until it naturally expires, maintaining unauthorized access.

MitigationUpgrade to AxxonSoft Axxon One version 2.0.3 or later. As a compensating control, consider reducing session lifetimes and implementing immediate session revocation mechanisms for administrative actions that modify user privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Axxon OneApplication
Affected:<= 2.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Axxon One installation and version
    Locate the Axxon One installation directory on the Windows system and check the version information, typically found in application metadata, About dialog, or installation logs
    Affected if The installed version is 2.0.2 or earlier (any version up to and including 2.0.2)
  2. Confirm Web Admin Panel is accessible
    Verify that the Axxon One Web Admin Panel interface is enabled and accessible on the network or locally
    Affected if The Web Admin Panel is exposed and users can authenticate to it
  3. Determine if user privilege management is in use
    Check if the Axxon One system has multiple user accounts with role-based access control configured in the administration settings
    Affected if The system uses role-based access control with users who have varying privilege levels
  4. Assess session token expiration settings
    Review the session configuration for the Web Admin Panel to determine the current session lifetime duration
    Affected if Session tokens have long expiration times (hours to days), increasing the window of unauthorized access after privilege revocation

You are affected if running Axxon One version 2.0.2 or earlier with the Web Admin Panel enabled, and users with changing privileges or roles exist in the system - the vulnerability allows former users to retain access via existing sessions until those sessions naturally expire.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.2
Interim mitigation

Upgrade to AxxonSoft Axxon One version 2.0.3 or later. As a compensating control, consider reducing session lifetimes and implementing immediate session revocation mechanisms for administrative actions that modify user privileges.

Recommended fix High confidence

2.0.3

  1. 1. Verify current Axxon One version is <= 2.0.2 by checking the Web Admin Panel or system information
  2. 2. Back up all Axxon One configuration data, databases, and any custom settings according to vendor backup procedures
  3. 3. Download Axxon One version 2.0.3 from the official AxxonSoft website (www.axxonsoft.com) or authorized distribution channel
  4. 4. Stop all Axxon One services and ensure no active recordings or operations are in progress
  5. 5. Install Axxon One 2.0.3 following the vendor's installation instructions for your Windows environment
  6. 6. Restore configuration from backup if needed after installation
  7. 7. Start Axxon One services and verify the application is running correctly
  8. 8. Test session expiration behavior in the Web Admin Panel to confirm the fix is working

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Axxon One Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10223 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data