CVE
October CMS server-side request forgery in Image Resizer
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
Summary
October CMS has a server-side request forgery flaw in its Image Resizer component, where manipulating the url argument can make the server send requests to destinations an attacker chooses. An attacker can reach it remotely over the network, but must log in with high-level privileges first.
Original description
A vulnerability was found in October CMS up to 4.4.6. This affects the function validateExternalImageHost of the file modules/system/classes/resizeimages/ValidatesExternalImages.php of the component Image Resizer. Performing a manipulation of the argument url results in server-side request forgery. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitability is reported as difficult. The exploit has been made public and could be used. Upgrading to version 4.4.7 mitigates this issue. The patch is named f6372867006c03141944e7b57396a726eb02acf0. You should upgrade the affected component.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.1/10CVSS 2.1
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132252 (October CMS Image Resizer ValidatesExternalImages.php validateExternalImageHost server-side request forgery), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132252 (entry last updated 2026-11-18):
Affected:
- October CMS: versions 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, 4.4.5, 4.4.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132252 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132252 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/octobercms/october/commit/f6372867006c03141944e7b57396a726eb02acf0
- https://github.com/octobercms/october/releases/tag/v4.4.7
- https://vuldb.com/vuln/439624
- https://vuldb.com/vuln/439624/cti
- https://vuldb.com/cve/CVE-2026-132252
- https://vuldb.com/submit/992821
- https://github.com/octobercms/october/security/advisories/GHSA-m9vh-rj4h-xp6v
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132252
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132252"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- October CMS
4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, 4.4.5, 4.4.6
Evidence 9
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · octobercms/october · Advisory GHSA-m9vh-rj4h-xp6v |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132252 |
| Record | NVD · CVE-2026-132252 |
| Other links 6 | |
| Advisory | VulDB · Advisory #439624 |
| Advisory | VulDB · Threat intelligence #439624 |
| Advisory | VulDB · CVE-2026-132252 record |
| Advisory | VulDB · Submission #992821 |
| Patch | GitHub · octobercms/october · Commit f6372867 |
| Patch | GitHub · octobercms/october · Release v4.4.7 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132252
Is CVE-2026-132252 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-132252?
CMS: versions 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4 and 2 more.Source: cve.now feed data