CWE-610: Externally Controlled Reference to a Resource in Skip to content

Security weakness

CWE-610 Externally Controlled Reference to a Resource in Another Sphere

A class-level weakness that can lead to private data exposed, data, pages or code changed and 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-610?

Externally Controlled Reference to a Resource in Another Sphere: The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.

Business impact

What CWE-610 could cost your business

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

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Read Application Data
  • Modify Application Data

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Read Application Data
  • Modify Application Data

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-610 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-610

Externally Controlled Reference to a Resource in Another Sphere

The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.

Weakness ID
CWE-610
Type
Class
Status
Draft
Introduced during
Architecture and Design

Detection and evidence

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

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

Real vulnerabilities it caused

  • CVE-2022-3032An email client does not block loading of remote objects in a nested document.
  • CVE-2022-45918Chain: a learning management tool debugger uses external input to locate previous session logs (CWE-73) and does not properly validate the given path (CWE-20), allowing for filesystem path traversal using "../" sequences.
  • CVE-2018-1000613Cryptography API uses unsafe reflection when deserializing a private key
  • CVE-2020-11053Chain: Go-based Oauth2 reverse proxy can send the authenticated user to another site at the end of the authentication flow. A redirect URL with HTML-encoded whitespace characters can bypass the validation (CWE-1289) to.
  • CVE-2022-42745Recruiter software allows reading arbitrary files using XXE
  • CVE-2004-2331Database system allows attackers to bypass sandbox restrictions by using the Reflection API.

How we fix it

From finding to fixed: how Codefreex closes CWE-610

  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-610: FAQs

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

What is CWE-610?

CWE-610, “Externally Controlled Reference to a Resource in Another Sphere”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.

How serious is CWE-610?

It can affect confidentiality, integrity, access control, with impacts such as read application data, modify application data, gain privileges or assume identity. The real risk depends on where the weakness sits and what data or functions it exposes.

Can Codefreex check my site for CWE-610?

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