What is CVE-2018-8031?

CVE-2018-8031 is a medium-severity cross-site scripting (XSS) vulnerability in org.apache.tomee:tomee-webapp (maven), affecting versions < 7.0.5. It is fixed in 7.0.5. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2018-8031?

CVE-2018-8031 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.tomee:tomee-webapp are affected by CVE-2018-8031?

org.apache.tomee:tomee-webapp (maven) versions < 7.0.5 is affected.

Is there a fix for CVE-2018-8031?

Yes. CVE-2018-8031 is fixed in 7.0.5. Upgrade to this version or later.

Is CVE-2018-8031 exploitable, and should I be worried?

Whether CVE-2018-8031 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2018-8031 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2018-8031 in org.apache.tomee:tomee-webapp

Q: How severe is CVE-2018-8031?

CVE-2018-8031 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.apache.tomee:tomee-webapp are affected by CVE-2018-8031?

org.apache.tomee:tomee-webapp (maven) versions < 7.0.5 is affected.

Q: Is there a fix for CVE-2018-8031?

Yes. CVE-2018-8031 is fixed in 7.0.5. Upgrade to this version or later.

Q: Is CVE-2018-8031 exploitable, and should I be worried?

Whether CVE-2018-8031 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2018-8031 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2018-8031?

Upgrade org.apache.tomee:tomee-webapp to 7.0.5 or later.

Summary

Apache TomEE console vulnerable to Cross-site Scripting

The Apache TomEE console (tomee-webapp) has a XSS vulnerability which could allow javascript to be executed if the user is given a malicious URL. This web application is typically used to add TomEE features to a Tomcat installation. The TomEE bundles do not ship with this application included. This issue can be mitigated by removing the application after TomEE is setup (if using the application to install TomEE), using one of the provided pre-configured bundles, or by upgrading to TomEE 7.0.5. This issue is resolved in this commit: b8bbf50c23ce97dd64f3a5d77f78f84e47579863.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2018-8031 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.0.5); upgrading removes the vulnerable code path.

Affected versions

org.apache.tomee:tomee-webapp (< 7.0.5)

Security releases

org.apache.tomee:tomee-webapp → 7.0.5 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.apache.tomee:tomee-webapp to 7.0.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2018-8031? CVE-2018-8031 is a medium-severity cross-site scripting (XSS) vulnerability in org.apache.tomee:tomee-webapp (maven), affecting versions < 7.0.5. It is fixed in 7.0.5. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2018-8031? CVE-2018-8031 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.apache.tomee:tomee-webapp are affected by CVE-2018-8031? org.apache.tomee:tomee-webapp (maven) versions < 7.0.5 is affected.
Is there a fix for CVE-2018-8031? Yes. CVE-2018-8031 is fixed in 7.0.5. Upgrade to this version or later.
Is CVE-2018-8031 exploitable, and should I be worried? Whether CVE-2018-8031 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2018-8031 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2018-8031? Upgrade org.apache.tomee:tomee-webapp to 7.0.5 or later.