CVE-2025-12063
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 · uneditedAn insecure direct object reference allowed a non-admin user to modify or remove certain data objects without having the appropriate permissions.
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 · moderate confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability where the application fails to properly validate user authorization when accessing or modifying data objects. A non-administrative user can directly reference object identifiers (such as database IDs or file paths) to alter or delete resources belonging to other users or protected by higher privilege levels.
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< 6.14.10768CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Axis Camera Station Pro versionCheck the installed version of Axis Camera Station Pro through the application interface (Help > About) or the Windows Programs and Features list. Compare the version number to the affected range: any version below 6.14.10768 is vulnerable.Affected if Installed version is less than 6.14.10768
-
Confirm application is running with multi-user accessDetermine if the system has multiple user accounts configured or if the application accepts connections from multiple clients. IDOR requires the presence of multiple user contexts to exploit.Affected if Multiple users or client connections are configured and the vulnerable version is installed
-
Identify accessible object referencesAs a non-administrative user, attempt to access API endpoints or application features that accept direct object identifiers (such as camera IDs, recording IDs, or user IDs in URLs or API parameters). Observe if unauthorized access to other users resources is possible.Affected if Non-administrative users can directly reference and access objects belonging to other users
A system is affected if it runs Axis Camera Station Pro version below 6.14.10768 and has multiple user accounts or client access enabled, allowing unauthorized object reference manipulation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.14.10768
Implement proper authorization checks on all endpoints that accept object references, preferably using indirect object references and verifying the current user's permissions before allowing any modification or deletion operations.
Camera Station Pro 6.14.10768 or later
- Check the current version of Axis Camera Station Pro installed on the system
- Access the Axis website at www.axis.com or use the Axis Device Manager to download the latest version
- Ensure you have admin credentials before performing the upgrade
- Backup the current system configuration and any important data
- Upgrade Camera Station Pro to version 6.14.10768 or later
- After upgrade, verify that non-admin users can no longer modify or remove data objects they should not have access to
- Confirm the new version is reflected in the software's About/Version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12063 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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