CWE-1047 Base Incomplete

Modules with Circular Dependencies

This weakness occurs when software modules have circular references, meaning Module A depends on Module B, which in turn depends back on Module A, creating a closed loop.

Definition

What is CWE-1047?

This weakness occurs when software modules have circular references, meaning Module A depends on Module B, which in turn depends back on Module A, creating a closed loop.
Circular dependencies create a tightly coupled architecture that undermines modular design. This makes the codebase significantly harder to understand, test, and maintain because changes in one module can unpredictably ripple through the entire cycle. For developers, this increases the time and complexity required to locate and fix bugs, including security vulnerabilities, making it easier to inadvertently introduce new flaws during maintenance. From a security perspective, this architectural flaw indirectly weakens your application's security posture. The reduced maintainability and increased complexity slow down vulnerability remediation, extending potential exposure windows. Furthermore, these cycles can cause runtime failures like stack overflows or initialization deadlocks. If an attacker can trigger these unreliable code paths, a stability issue can be directly exploited as a security vulnerability.
Real-world impact

Real-world CVEs caused by CWE-1047

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-1047

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Detection signals

How to detect CWE-1047

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-1047 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-1047?

This weakness occurs when software modules have circular references, meaning Module A depends on Module B, which in turn depends back on Module A, creating a closed loop.

How serious is CWE-1047?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-1047?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-1047?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

How does Plexicus detect and fix CWE-1047?

Plexicus's SAST engine matches the data-flow signature for CWE-1047 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-1047?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/1047.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-1047

CWE-1120 Parent

Excessive Code Complexity

This weakness occurs when software contains sections of code that are unnecessarily intricate, as measured by established complexity…

CWE-1056 Sibling

Invokable Control Element with Variadic Parameters

This weakness occurs when a callable function or method is defined to accept a variable number of arguments (variadic parameters).

CWE-1060 Sibling

Excessive Number of Inefficient Server-Side Data Accesses

This weakness occurs when an application makes an excessive number of individual data queries to a server or database, instead of using…

CWE-1064 Sibling

Invokable Control Element with Signature Containing an Excessive Number of Parameters

This weakness occurs when a function, method, or subroutine is defined with an unnecessarily high number of parameters in its signature.

CWE-1075 Sibling

Unconditional Control Flow Transfer outside of Switch Block

This weakness occurs when code uses an unconditional jump, like a 'goto' statement, outside of a structured control flow block like a…

CWE-1080 Sibling

Source Code File with Excessive Number of Lines of Code

This weakness occurs when a single source code file grows excessively large, containing too many lines of code.

CWE-1095 Sibling

Loop Condition Value Update within the Loop

This vulnerability occurs when a loop's exit condition depends on a variable that is also modified inside the loop body. This creates a…

CWE-1119 Sibling

Excessive Use of Unconditional Branching

This weakness occurs when code relies heavily on unconditional jumps like 'goto' statements, making the program flow difficult to follow.

CWE-1121 Sibling

Excessive McCabe Cyclomatic Complexity

This weakness occurs when a function or method has an overly complex control flow, measured by a high McCabe Cyclomatic Complexity score.…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo