Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-83 Variant Draft
Improper Neutralization of Script in Attributes in a Web Page
This vulnerability occurs when a web application fails to properly sanitize or block JavaScript URIs (like 'javascript:') within HTML tag attributes. Attackers can inject malicious code into…
Definition
What is CWE-83?
This vulnerability occurs when a web application fails to properly sanitize or block JavaScript URIs (like 'javascript:') within HTML tag attributes. Attackers can inject malicious code into attributes such as onmouseover, onload, onerror, or style, leading to cross-site scripting (XSS) attacks when the page renders.
This flaw is a specific type of Cross-Site Scripting (XSS) where the injection point is not within the main HTML content, but within an element's attribute values. Unlike standard reflected XSS, the malicious script is often triggered by a user interaction (like moving a mouse) or a page event (like an image failing to load), making it harder to detect during casual testing. Developers might overlook these attributes when implementing input validation or output encoding filters.
To prevent this, you must treat all user-supplied data placed into HTML attributes as untrusted. Implement context-sensitive output encoding specifically for HTML attributes before inserting data. Use a reputable security library for this encoding, as different contexts (HTML, JavaScript, CSS) require different escaping rules. Additionally, consider implementing a Content Security Policy (CSP) as a robust defense-in-depth measure to block the execution of inline JavaScript.
Real-world impact
Real-world CVEs caused by CWE-83
-
Bypass filtering of SCRIPT tags using onload in BODY, href in A, BUTTON, INPUT, and others.
-
guestbook XSS in STYLE or IMG SRC attributes.
-
Javascript in onerror attribute of IMG tag.
-
XSS in web-based email product via onmouseover event.
-
XSS via script in tag.
-
Onload, onmouseover, and other events in an e-mail attachment.
-
Onmouseover and onload events in img, link, and mail tags.
-
Javascript in onmouseover attribute in e-mail address or URL.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 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.
// 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
// 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-83
- Implementation Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including tag attributes, hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.
- Implementation Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component. The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.
- Implementation With Struts, write all data from form beans with the bean's filter attribute set to true.
- Implementation To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.
Detection signals
How to detect CWE-83
Plexicus auto-detects CWE-83 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.
Frequently asked questions What is CWE-83?
How serious is CWE-83?
What languages or platforms are affected by CWE-83?
How can I prevent CWE-83?
How does Plexicus detect and fix CWE-83?
Where can I learn more about CWE-83?
Frequently asked questions
What is CWE-83?
This vulnerability occurs when a web application fails to properly sanitize or block JavaScript URIs (like 'javascript:') within HTML tag attributes. Attackers can inject malicious code into attributes such as onmouseover, onload, onerror, or style, leading to cross-site scripting (XSS) attacks when the page renders.
How serious is CWE-83?
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-83?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-83?
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including tag attributes, hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We…
How does Plexicus detect and fix CWE-83?
Plexicus's SAST engine matches the data-flow signature for CWE-83 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-83?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/83.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-83
CWE-79 Parent
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
This vulnerability occurs when a web application fails to properly sanitize or encode user-supplied input before displaying it on a…
CWE-80 Sibling
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
This vulnerability, commonly known as Basic Cross-Site Scripting (XSS), occurs when a web application fails to properly sanitize user…
CWE-81 Sibling
Improper Neutralization of Script in an Error Message Web Page
This vulnerability occurs when an application fails to properly sanitize user-supplied input before displaying it within an error message…
CWE-84 Sibling
Improper Neutralization of Encoded URI Schemes in a Web Page
This vulnerability occurs when a web application fails to properly sanitize user-supplied input that contains malicious scripts disguised…
CWE-85 Sibling
Doubled Character XSS Manipulations
This vulnerability occurs when a web application fails to properly sanitize user input that contains doubled characters, allowing…
CWE-86 Sibling
Improper Neutralization of Invalid Characters in Identifiers in Web Pages
This vulnerability occurs when an application fails to properly filter or escape invalid characters within web identifiers like HTML tag…
CWE-87 Sibling
Improper Neutralization of Alternate XSS Syntax
This vulnerability occurs when an application fails to properly sanitize user-supplied input that uses alternative methods to execute…
CWE-82 Child
Improper Neutralization of Script in Attributes of IMG Tags in a Web Page
This vulnerability occurs when a web application fails to properly sanitize or escape script code within the attributes of HTML IMG tags,…
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.