How severe is CVE-2015-5612?

No CVSS score has been assigned to CVE-2015-5612 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-5612?

CVE-2015-5612 affects the following packages: october/october (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2015-5612?

Update october/october to 1.0.319 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5612 is resolved across your whole dependency graph.

How do I detect CVE-2015-5612 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/october, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-5612 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2015-5612 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-5612 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-5612?

CVE-2015-5612 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-5612?

CVE-2015-5612 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2015-5612 published, and has it been updated?

CVE-2015-5612 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2015-5612 — october

Fix: octobercms/october@8a4ac53

CVE-2015-5612 is a Cross-site Scripting (XSS) vulnerability in october/october. A fix is available for october/october — see the affected versions and patch details below.

October CMS XSS In Caption Tag of Profile

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘october/october

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Cross-site scripting (XSS) vulnerability in October CMS build 271 and earlier allows remote attackers to inject arbitrary web script or HTML via the caption tag of a profile image.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`october/october`	all versions	1.0.319`composer require october/october:^1.0.319`

Affected Products

1 product · 1 configurations

Application

octoberoctobercms

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/october, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update october/october to 1.0.319 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5612 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Cross-site scripting (XSS) vulnerability in October CMS build 271 and earlier allows remote attackers to inject arbitrary web script or HTML via the caption tag of a profile image.

O3 Security · Impact-Aware SCA

Is CVE-2015-5612 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works