What is the severity of CVE-2013-5379?

CVE-2013-5379 is classified as a medium severity vulnerability due to its potential for cross-site scripting (XSS) attacks.

How do I fix CVE-2013-5379?

To fix CVE-2013-5379, ensure that your IBM WebSphere Portal is updated to version 7.0.0.2 CF25 or 8.0.0.1 CF8 or later.

Who is affected by CVE-2013-5379?

CVE-2013-5379 affects IBM WebSphere Portal versions 7.0.0.0, 7.0.0.1, 7.0.0.2, 8.0.0.0, and 8.0.0.1.

What type of vulnerability is CVE-2013-5379?

CVE-2013-5379 is a cross-site scripting (XSS) vulnerability that allows remote authenticated users to inject arbitrary script or HTML.

Can CVE-2013-5379 be exploited remotely?

Yes, CVE-2013-5379 can be exploited remotely by authenticated users through improper tagging functionality.

Vulnerability/
CVE-2013-5379

low

3.5

CWE

13/11/2013

6/8/2024

CVE-2013-5379: XSS

First published: Wed Nov 13 2013(Updated: )

Cross-site scripting (XSS) vulnerability in IBM WebSphere Portal 7.x before 7.0.0.2 CF25 and 8.x before 8.0.0.1 CF8 allows remote authenticated users to inject arbitrary web script or HTML by leveraging improper tagging functionality.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM WebSphere Portal	=7.0.0.0
IBM WebSphere Portal	=7.0.0.1
IBM WebSphere Portal	=7.0.0.2
IBM WebSphere Portal	=8.0.0.0
IBM WebSphere Portal	=8.0.0.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-5379?
CVE-2013-5379 is classified as a medium severity vulnerability due to its potential for cross-site scripting (XSS) attacks.
How do I fix CVE-2013-5379?
To fix CVE-2013-5379, ensure that your IBM WebSphere Portal is updated to version 7.0.0.2 CF25 or 8.0.0.1 CF8 or later.
Who is affected by CVE-2013-5379?
CVE-2013-5379 affects IBM WebSphere Portal versions 7.0.0.0, 7.0.0.1, 7.0.0.2, 8.0.0.0, and 8.0.0.1.
What type of vulnerability is CVE-2013-5379?
CVE-2013-5379 is a cross-site scripting (XSS) vulnerability that allows remote authenticated users to inject arbitrary script or HTML.
Can CVE-2013-5379 be exploited remotely?
Yes, CVE-2013-5379 can be exploited remotely by authenticated users through improper tagging functionality.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/last-modified-date
agent/author
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
agent/weakness
vendor/ibm
canonical/ibm websphere portal
version/ibm websphere portal/7.0.0.0
version/ibm websphere portal/7.0.0.1
version/ibm websphere portal/7.0.0.2
version/ibm websphere portal/8.0.0.0
version/ibm websphere portal/8.0.0.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2013-5379?
CVE-2013-5379 is classified as a medium severity vulnerability due to its potential for cross-site scripting (XSS) attacks.
How do I fix CVE-2013-5379?
To fix CVE-2013-5379, ensure that your IBM WebSphere Portal is updated to version 7.0.0.2 CF25 or 8.0.0.1 CF8 or later.
Who is affected by CVE-2013-5379?
CVE-2013-5379 affects IBM WebSphere Portal versions 7.0.0.0, 7.0.0.1, 7.0.0.2, 8.0.0.0, and 8.0.0.1.
What type of vulnerability is CVE-2013-5379?
CVE-2013-5379 is a cross-site scripting (XSS) vulnerability that allows remote authenticated users to inject arbitrary script or HTML.
Can CVE-2013-5379 be exploited remotely?
Yes, CVE-2013-5379 can be exploited remotely by authenticated users through improper tagging functionality.