LiveActive security incident?Get immediate response
CVE Record

CVE-2023-5800: Insufficient input validation in VAPIX API create_overlay.cgi

Vintage, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API create_overlay.cgi did not have a sufficient input validation allowing for a possible remote code execution. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects certain AXIS OS versions used on Axis devices. An authenticated operator or administrator service account could abuse weak input validation in the VAPIX create_overlay.cgi API, potentially causing remote code execution. The need for valid privileged credentials lowers urgency, but exposed or shared service accounts increase business risk.

Executive priority

Treat this as a moderate priority patching and credential hygiene issue. It is not sourced as actively exploited, but authenticated code execution risk on camera or device infrastructure can become serious if privileged service accounts are compromised.

Technical view

CVE-2023-5800 is insufficient input validation in AXIS OS VAPIX API create_overlay.cgi, mapped to CWE-35. Axis describes possible remote code execution after authentication with an operator- or administrator-privileged service account. CVSS v3.1 is 5.4 with network access, low complexity, low privileges, no user interaction, and limited integrity and availability impact.

Likely exposure

Likely exposure is Axis devices running AXIS OS 11.8, 10.12, 9.80, 8.40, or 6.50 where operator or administrator service accounts can authenticate to VAPIX.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires authenticated operator- or administrator-level service account access, so stolen, shared, or overprivileged service credentials are the main concern.

Researcher notes

The public bundle does not provide exploit details, fixed build numbers, or a proof-of-concept. Analysis should focus on affected AXIS OS identification, VAPIX authentication exposure, service-account privilege review, and vendor advisory confirmation.

Mitigation direction

  • Apply the patched AXIS OS versions referenced by Axis guidance.
  • Prioritize devices running the listed affected AXIS OS versions.
  • Review operator and administrator service accounts for necessity.
  • Remove or rotate shared, stale, or overprivileged service credentials.
  • Consult the Axis advisory for exact fixed versions and deployment guidance.

Validation and detection

  • Inventory Axis devices and record AXIS OS versions.
  • Check whether devices run AXIS OS 11.8, 10.12, 9.80, 8.40, or 6.50.
  • Confirm VAPIX access requires valid service account authentication.
  • Verify patched AXIS OS builds are installed after remediation.
  • Review service account permissions for operator or administrator privileges.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-35: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-5800 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-5800Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Axis Communications ABAXIS OSAXIS OS 11.8, 10.12, 9.80, 8.40, 6.50unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-35 · source CWE mapping

Path Traversal: '.../...//'

Path Traversal: '.../...//' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.