What is the CVSS score of CVE-2014-7264?

CVE-2014-7264 has a CVSS 2.0 base score of 3.5 (Low). CVSS vector: AV:N/AC:M/Au:S/C:N/I:P/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2014-7264?

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

Chyrp CVE-2014-7264

LOW

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

2014-12-11 vultures@jpcert.or.jp

XSS Chyrp

3.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

3.5 LOW

AV:N/AC:M/Au:S/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:S/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Dec 11, 2014 - 23:59 cve.org

LOW 3.5

DescriptionCVE.org

Multiple cross-site scripting (XSS) vulnerabilities in admin/themes/default/pages/manage_users.twig in the Users Management feature in the admin component in Chyrp before 2.5.1 allow remote authenticated users to inject arbitrary web script or HTML via the (1) user.email or (2) user.website field in a user registration.

AnalysisAI

Multiple cross-site scripting (XSS) vulnerabilities in admin/themes/default/pages/manage_users.twig in the Users Management feature in the admin component in Chyrp before 2.5.1 allow remote. Rated low severity (CVSS 3.5), 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. Multiple cross-site scripting (XSS) vulnerabilities in admin/themes/default/pages/manage_users.twig in the Users Management feature in the admin component in Chyrp before 2.5.1 allow remote authenticated users to inject arbitrary web script or HTML via the (1) user.email or (2) user.website field in a user registration. Affected products include: Chyrp. Version information: before 2.5.1.

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.