What CVEs are caused by CWE-1263?

12 recorded CVEs are attributed to CWE-1263, including CVE-2024-48973, CVE-2023-38290, CVE-2024-36438.

What are the consequences of CWE-1263?

Exploiting CWE-1263 can lead to: Varies by Context.

Is CWE-1263 actively exploited?

12 recorded CVEs are caused by CWE-1263; none are currently in CISA's KEV catalog of actively exploited flaws.

Class weakness

Incomplete

CWE-1263: Improper Physical Access Control

The product is designed with access restricted to certain information, but it does not sufficiently protect against an unauthorized actor with physical access to these areas.

Last updated May 1, 2026

Recorded CVEs

With this primary weakness

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Class

Abstraction

MITRE classification

Overview

Sections of a product intended to have restricted access may be inadvertently or intentionally rendered accessible when the implemented physical protections are insufficient. The specific requirements around how robust the design of the physical protection mechanism needs to be depends on the type of product being protected. Selecting the correct physical protection mechanism and properly enforcing it through implementation and manufacturing are critical to the overall physical security of the product.

Real-world CVEs

12 recorded CVEs are caused by CWE-1263 (Improper Physical Access Control). The highest-severity and most recent are shown first. 1 new CWE-1263 CVE has been recorded so far in 2026 (2 in 2025).

Common consequences

What can happen when CWE-1263 is exploited.

Varies by Context

Affects: Confidentiality, Integrity, Access Control

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

Manufacturing

How to prevent it

Practical mitigations for CWE-1263, grouped by where in the lifecycle they apply.

Architecture and Design

Specific protection requirements depend strongly on contextual factors including the level of acceptable risk associated with compromise to the product's protection mechanism. Designers could incorporate anti-tampering measures that protect against or detect when the product has been tampered with.

Testing

The testing phase of the lifecycle should establish a method for determining whether the protection mechanism is sufficient to prevent unauthorized access.

Manufacturing

Ensure that all protection mechanisms are fully activated at the time of manufacturing and distribution.

Attack patterns

CAPEC attack patterns that exploit this weakness.

CAPEC-401: Physically Hacking Hardware

Frequently asked questions

Common questions about CWE-1263.

What is CWE-1263?: The product is designed with access restricted to certain information, but it does not sufficiently protect against an unauthorized actor with physical access to these areas.
What CVEs are caused by CWE-1263?: 12 recorded CVEs are attributed to CWE-1263, including CVE-2024-48973, CVE-2023-38290, CVE-2024-36438.
How do you prevent CWE-1263?: Specific protection requirements depend strongly on contextual factors including the level of acceptable risk associated with compromise to the product's protection mechanism. Designers could incorporate anti-tampering measures that protect against or detect when the product has been tampered with.
What are the consequences of CWE-1263?: Exploiting CWE-1263 can lead to: Varies by Context.
Is CWE-1263 actively exploited?: 12 recorded CVEs are caused by CWE-1263; none are currently in CISA's KEV catalog of actively exploited flaws.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.

Stay ahead of CWE-1263

Get alerted the moment a new CWE-1263 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing