CWE-268: Privilege Chaining | Causes and Fixes Skip to content

Security weakness

CWE-268 Privilege Chaining

A base-level weakness that can lead to accounts and admin areas exposed. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-268?

Privilege Chaining: Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination.

Business impact

What CWE-268 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Access Control

Accounts and admin areas exposed

Logins and permission checks can be bypassed, putting admin and customer accounts at risk.

  • Gain Privileges or Assume Identity

Free security check

Is CWE-268 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-268

Privilege Chaining

Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination.

Weakness ID
CWE-268
Type
Base
Status
Draft
Likelihood of exploit
High
Introduced during
Architecture and Design, Implementation, Operation

Prevention

How to fix CWE-268, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
    • Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
    • Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to.

Detection and evidence

How CWE-268 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

Real vulnerabilities it caused

  • CVE-2005-1736Chaining of user rights.
  • CVE-2002-1772Gain certain rights via privilege chaining in alternate channel.
  • CVE-2005-1973Application is allowed to assign extra permissions to itself.
  • CVE-2003-0640"operator" user can overwrite usernames and passwords to gain admin privileges.

How we fix it

From finding to fixed: how Codefreex closes CWE-268

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

Related weaknesses

FAQ

CWE-268: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-268?

CWE-268, “Privilege Chaining”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination.

How serious is CWE-268?

MITRE rates the likelihood of exploit as High. It can affect access control, with impacts such as gain privileges or assume identity. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-268?

Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource. Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

Can Codefreex check my site for CWE-268?

Yes. A senior engineer reviews your site, store or app for CWE-268 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-268 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.