Opensymphony has a narrow vulnerability footprint centered on its web application framework products XWork and WebWork, with observed weaknesses clustering around information exposure, input validation, and cross-site scripting issues endemic to request-handling and templating layers. Treat this as a compact vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Opensymphony over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2008-6504MEDIUM ParametersInterceptor in OpenSymphony XWork 2.0.x before 2.0.6 and 2.1.x before 2.1.2, as used in Apache Struts and other products, does not properly restrict # (pound sign) refere | Mar 23, 2009 | 5.0 | 42 | NO | YES |
CVE-2007-4556MEDIUM Struts support in OpenSymphony XWork before 1.2.3, and 2.x before 2.0.4, as used in WebWork and Apache Struts, recursively evaluates all input as an Object-Graph Navigation Languag | Aug 28, 2007 | 6.8 | 39 | NO | YES |
Multiple cross-site scripting (XSS) vulnerabilities in XWork in Apache Struts 2.x before 2.2.3, and OpenSymphony XWork in OpenSymphony WebWork, allow remote attackers to inject arb | May 13, 2011 | 2.6 | 38 | NO | YES |
CVE-2011-2088MEDIUM XWork 2.2.1 in Apache Struts 2.2.1, and OpenSymphony XWork in OpenSymphony WebWork, allows remote attackers to obtain potentially sensitive information about internal Java class pa | May 13, 2011 | 5.0 | 18 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Opensymphony.
Media articles that mention a CVE ID that affects a product developed by Opensymphony — matched by CVE ID, not by vendor name.