Camera Station ProApplication · Axis

CVE-2025-1056

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-23
Fix available
A fix is available. Upgrade to 6.8.43213 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Gee-netics, member of AXIS Camera Station Pro Bug Bounty Program, has identified an issue with a specific file that the server is using. A non-admin user can modify this file to either create files or change the content of files in an admin-protected location. Axis has released a patched version for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.

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 confidence

A file permission vulnerability in AXIS Camera Station Pro allows a non-admin user to modify a specific file that the server uses. By modifying this file, an attacker can create new files or overwrite content in admin-protected locations, achieving privilege escalation from standard user to administrator-level file system access.

MitigationApply the vendor-provided security patch from the Axis security advisory to the affected AXIS Camera Station Pro installation, and verify that file permissions prevent non-admin users from modifying server-used configuration or runtime files.

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
Camera Station ProApplication
Affected:< 6.8.43213

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/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 checks

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

  1. Check installed AXIS Camera Station Pro version
    Open AXIS Camera Station Pro client, go to Help > About, or check the Windows Programs and Features list for the installed version number
    Affected if The version listed is lower than 6.8.43213 (e.g., 6.8.x below 6.8.43213, or any earlier major version)
  2. Identify server-used configuration or runtime files
    Locate the AXIS Camera Station Pro installation directory (typically C:\Program Files\Axis Communications\AXIS Camera Station Pro\ or C:\ProgramData\Axis Communications\AXIS Camera Station\), and identify XML, config, or runtime files used by the server service
    Affected if Non-admin users have write permissions to any file that the AXIS Camera Station server reads or executes on startup
  3. Test non-admin user file write permissions
    Using a standard (non-privileged) Windows account, attempt to create or modify files within the AXIS Camera Station Pro installation directories and program data folders
    Affected if A standard user account can successfully write or modify files in directories that the server application uses
  4. Check file ownership and ACLs on application directories
    Right-click the AXIS Camera Station Pro folders, select Properties > Security tab, and verify that Users or standard accounts are not granted Write or Modify permissions to server configuration directories
    Affected if The Users group or standard user accounts have Write or Modify permissions on directories containing server-used files

If the installed version is below 6.8.43213 AND non-admin users can write to server-used files or directories, the environment is vulnerable to privilege escalation via this file permission flaw.

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 6.8.43213 or later
Fixed in 6.8.43213
Interim mitigation

Apply the vendor-provided security patch from the Axis security advisory to the affected AXIS Camera Station Pro installation, and verify that file permissions prevent non-admin users from modifying server-used configuration or runtime files.

Recommended fix Moderate confidence

6.8.43213 or later

  1. Identify the current version of AXIS Camera Station Pro installed
  2. Navigate to the official AXIS support website or the security advisory at www.axis.com
  3. Locate and download the patched version (6.8.43213 or later)
  4. Back up the current Camera Station configuration and database
  5. Install the patched version following the standard AXIS upgrade procedure
  6. Verify the installation was successful and the version is now 6.8.43213 or higher
  7. Test that non-admin users can no longer modify files in admin-protected locations

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

Fix this in Camera Station Pro Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1056 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1056 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