The web application sends a redirect to another location, but instead of exiting, it executes additional code.
View on MITREThis weakness could affect the control flow of the application and allow execution of untrusted code.
No mitigation information available for this CWE.
This issue might not be detected if testing is performed using a web browser, because the browser might obey the redirect and move the user to a different page before the application has produced outputs that indicate something is amiss.
This code queries a server and displays its status when a request comes from an authorized IP address.
This code redirects unauthorized users, but continues to execute code after calling http_redirect(). This means even unauthorized users may be able to access the contents of the page or perform a DoS attack on the server being queried. Also, note that this code is vulnerable to an IP address spoofing attack (CWE-212).
$requestingIP = $_SERVER['REMOTE_ADDR'];if(!in_array($requestingIP,$ipAllowList)){echo "You are not authorized to view this page";http_redirect($errorPageURL);}$status = getServerStatus();echo $status; ...Execution-after-redirect allows access to application configuration details.
View Detailschain: library file sends a redirect if it is directly requested but continues to execute, allowing remote file inclusion and path traversal.
View DetailsRemote attackers can obtain access to administrator functionality through EAR.
View DetailsRemote attackers can obtain access to administrator functionality through EAR.
View Detailschain: execution after redirect allows non-administrator to perform static code injection.
View DetailsAdditional facts reviewed against primary or authoritative security sources.
Documented detection approaches include Black Box; recorded impacts include Alter Execution Logic, and Execute Unauthorized Code or Commands; observed examples include CVE-2013-1402, CVE-2009-1936, and CVE-2007-2713. Use these source-defined anchors to turn CWE-698 into implementation, review, and verification checks for the affected component.
CWE-698: Execution After Redirect (EAR) — MITRE CWEUse NIST SSDF practices to make prevention of CWE-698, Execution After Redirect (EAR), an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.
NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and TechnologyUse CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-698, Execution After Redirect (EAR), has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.
Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security AgencyApply MITRE's full root-cause mapping guidance when using CWE-698, Execution After Redirect (EAR). Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.
CVE to CWE Root Cause Mapping Guidance — MITRE CWEApply MITRE's root-cause mapping quick tips to CWE-698, Execution After Redirect (EAR). Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.
CVE to CWE Root Cause Mapping Quick Tips — MITRE CWECWE-698: Execution After Redirect (EAR) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The web application sends a redirect to another location, but instead of exiting, it executes additional code.
If exploited, CWE-698 (Execution After Redirect (EAR)) it can compromise Other, Confidentiality, Integrity and Availability, leading to outcomes such as Alter Execution Logic and Execute Unauthorized Code or Commands.
CWE-698 can be detected using Black Box. Combining automated tooling with manual review typically yields the best coverage.
CWE-698 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
MITRE documents real CVEs mapped to CWE-698, including CVE-2013-1402, CVE-2009-1936, CVE-2007-2713, CVE-2007-4932 and CVE-2007-5578. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-698 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.