CWE-795 Base Incomplete

Only Filtering Special Elements at a Specified Location

This vulnerability occurs when a security filter only checks for dangerous input patterns at specific, predefined locations within the data. It fails to scan the entire input stream, allowing…

Definition

What is CWE-795?

This vulnerability occurs when a security filter only checks for dangerous input patterns at specific, predefined locations within the data. It fails to scan the entire input stream, allowing malicious elements that appear outside the expected location to pass through and potentially harm downstream components.
Imagine a filter designed to remove semicolons, but it only checks the very beginning of a user-supplied string. An attacker can simply place the semicolon later in the input—for example, in the middle or at the end—to bypass the filter entirely. This creates a false sense of security because the filter is active, but its limited scope leaves the application exposed to the very attacks it was meant to prevent. This often happens when validation logic uses functions that only look for special characters at absolute positions (like 'byte 10') or relative to markers (like 'the second argument'). Developers must ensure their input sanitization processes perform a comprehensive check across the entire data payload, not just a single, predictable spot. The core failure is a logic error in the filter's design, not the absence of a filter.
Real-world impact

Real-world CVEs caused by CWE-795

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

    The following code takes untrusted input and uses a regular expression to filter a "../" element located at the beginning of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.

  2. 2

    Since the regular expression is only looking for an instance of "../" at the beginning of the string, it only removes the first "../" element. So an input value such as:

  3. 3

    will have the first "../" stripped, resulting in:

  4. 4

    This value is then concatenated with the /home/user/ directory:

  5. 5

    which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-22).

Vulnerable code example

Vulnerable Perl

The following code takes untrusted input and uses a regular expression to filter a "../" element located at the beginning of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.

Vulnerable Perl 
my $Username = GetUntrustedInput();
  $Username =~ s/^\.\.\///;
  my $filename = "/home/user/" . $Username;
  ReadAndSendFile($filename);
Attacker payload

Since the regular expression is only looking for an instance of "../" at the beginning of the string, it only removes the first "../" element. So an input value such as:

Attacker payload 
../../../etc/passwd
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-795

  • 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-795

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

This vulnerability occurs when a security filter only checks for dangerous input patterns at specific, predefined locations within the data. It fails to scan the entire input stream, allowing malicious elements that appear outside the expected location to pass through and potentially harm downstream components.

How serious is CWE-795?

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

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

How can I prevent CWE-795?

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

Plexicus's SAST engine matches the data-flow signature for CWE-795 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-795?

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

Related weaknesses

Weaknesses related to CWE-795

CWE-791 Parent

Incomplete Filtering of Special Elements

This vulnerability occurs when an application accepts data from a source but fails to properly clean or neutralize all special characters…

CWE-792 Sibling

Incomplete Filtering of One or More Instances of Special Elements

This vulnerability occurs when an application receives external data but fails to properly neutralize all instances of potentially…

CWE-796 Child

Only Filtering Special Elements Relative to a Marker

This vulnerability occurs when software filters dangerous inputs or characters, but only checks for them in specific, expected locations…

CWE-797 Child

Only Filtering Special Elements at an Absolute Position

This vulnerability occurs when software checks for dangerous characters or patterns only at a fixed, hardcoded location in input data.…

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.