CWE-940: Improper Verification of Source of a Skip to content

Security weakness

CWE-940 Improper Verification of Source of a Communication Channel

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-940?

Improper Verification of Source of a Communication Channel: The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.

Business impact

What CWE-940 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
  • Bypass Protection Mechanism

Free security check

Is CWE-940 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-940

Improper Verification of Source of a Communication Channel

The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.

Weakness ID
CWE-940
Type
Base
Status
Incomplete
Applies to
Mobile
Introduced during
Architecture and Design, Implementation

Prevention

How to fix CWE-940, phase by phase

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

  1. 01

    Architecture and Design

    • Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack. When designing functionality of actions in the URL scheme, consider whether the action should be accessible to all mobile applications, or if an allowlist of.

Detection and evidence

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

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

Real vulnerabilities it caused

  • CVE-2025-3651desktop product does not properly verify the source of a communication channel, allowing command execution
  • CVE-2000-1218DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning
  • CVE-2005-0877DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning
  • CVE-2001-1452DNS server caches glue records received from non-delegated name servers

How we fix it

From finding to fixed: how Codefreex closes CWE-940

  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.

FAQ

CWE-940: FAQs

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

What is CWE-940?

CWE-940, “Improper Verification of Source of a Communication Channel”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.

How serious is CWE-940?

It can affect access control, other, with impacts such as gain privileges or assume identity, varies by context, bypass protection mechanism. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-940?

Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack. When designing functionality of actions in.

Can Codefreex check my site for CWE-940?

Yes. A senior engineer reviews your site, store or app for CWE-940 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.

Which technologies does CWE-940 affect?

MITRE lists it as applicable to Mobile. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-940 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.