What is the CVSS score of CVE-2013-0181?

CVE-2013-0181 has a CVSS 2.0 base score of 2.6 (Low). CVSS vector: AV:N/AC:H/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.5%.

Is there a patch available for CVE-2013-0181?

Yes, a patch is available for CVE-2013-0181. Update the affected software to the latest version immediately.

Search Api CVE-2013-0181

LOW

Cross-site Scripting (XSS) (CWE-79)

2013-03-27 secalert@redhat.com

XSS Search Api

2.6

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.6 LOW

AV:N/AC:H/Au:N/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:H/Au:N/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

High

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Mar 27, 2013 - 21:55 cve.org

LOW 2.6

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in Views in the Search API (search_api) module 7.x-1.x before 7.x-1.4 for Drupal, when using certain backends and facets, allows remote attackers to inject arbitrary web script or HTML via unspecified input, which is returned in an error message.

AnalysisAI

Cross-site scripting (XSS) vulnerability in Views in the Search API (search_api) module 7.x-1.x before 7.x-1.4 for Drupal, when using certain backends and facets, allows remote attackers to inject. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Cross-site scripting (XSS) vulnerability in Views in the Search API (search_api) module 7.x-1.x before 7.x-1.4 for Drupal, when using certain backends and facets, allows remote attackers to inject arbitrary web script or HTML via unspecified input, which is returned in an error message. Affected products include: Thomas Seidl Search Api. Version information: before 7..

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.