XSS vulnerability in the MVCBean JSP portlet maven archetype
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Portals | affected |
|
No data.
No data available yet.
Vendor Workaround
If a project was generated from the affected maven archetype using a command like the following: mvn archetype:generate \ -DarchetypeGroupId=org.apache.portals.pluto.archetype \ -DarchetypeArtifactId=mvcbean-jsp-portlet-archetype \ -DarchetypeVersion=3.1.0 \ -DgroupId=com.mycompany \ -DartifactId=com.mycompany.my.mvcbean.jsp.portlet Then developers must fix the generated greeting.jspx file by escaping the rendered values submitted to the "First Name" and "Last Name" fields. For example, change: <span>${user.firstName} ${user.lastName}! </span> To: <span>${mvc.encoders.html(user.firstName)} ${mvc.encoders.html(user.lastName)}! </span> Moving forward, all such projects should be generated from version 3.1.1 of the Maven archetype.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-3qp6-m7hp-jrwf | Cross-site Scripting in Apache Pluto |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.4% (2.404% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|