Authenticated authorization bypass via trusted identifiers
Published Dec 11, 2025 · Updated Dec 11, 2025
Authorization bypass in AX Onboard 3.2.0 through 3.2.x allows remote authenticated users to access protected actions via trusted identifiers. The published record identifies a user-controlled key authorization failure but does not disclose the affected endpoint, parameter, record type, or omitted ownership check. A low-privileged authenticated account and network access are required; the CNA does not identify the affected data or authorized operation.
Summary
What happened
Authorization bypass in AX Onboard 3.2.0 through 3.2.x allows remote authenticated users to access protected actions via trusted identifiers. The published record identifies a user-controlled key authorization failure but does not disclose the affected endpoint, parameter, record type, or omitted ownership check. A low-privileged authenticated account and network access are required; the CNA does not identify the affected data or authorized operation.
The record
- CVE
- CVE-2025-13003
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- Aksis Computer Services and Consulting Inc.
- Product
- AX Onboard
- Classifications
- CWE-639, CAPEC-21
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 11, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.2.0 <3.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo