CVE-2026-36759
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Server-Side Request Forgery (SSRF) in the /themes/{name}/upgrade-from-uri endpoint of halo v2.22.14 allows authenticated attackers to scan internal resources via a crafted GET request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in the halo CMS platform. The /themes/{name}/upgrade-from-uri endpoint accepts user-controlled URI input without proper validation, allowing authenticated attackers to make the server perform requests to arbitrary internal or external resources. This can be leveraged to scan internal network services, access cloud metadata endpoints, or interact with internal APIs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed halo CMS versionCheck the application's version by reviewing the halo installation directory, package.json, or the admin interface version information. Compare your installed version against known halo CMS releases.Affected if Your halo CMS version is unpatched and the vendor has not released a security update for this vulnerability.
-
Verify the themes endpoint existsLocate the halo CMS web application files and confirm the presence of the theme upgrade routing handlers, specifically the endpoint pattern /themes/{name}/upgrade-from-uri. This is typically found in the routing configuration or controller definitions.Affected if The vulnerable endpoint handler exists in your installation and is accessible via the web server.
-
Confirm authentication is requiredReview your halo CMS authentication configuration to determine if access to the /themes/{name}/upgrade-from-uri endpoint requires valid user credentials. Check user role permissions and session handling settings.Affected if The endpoint permits unauthenticated access, meaning any user can trigger the SSRF without credentials.
-
Check theme installation statusList all installed themes in your halo CMS instance via the admin panel or by examining the themes directory. The vulnerable endpoint requires a valid theme name parameter.Affected if At least one theme is installed and active, providing a valid parameter value for the /themes/{name}/upgrade-from-uri endpoint.
You are affected if your halo CMS version contains the vulnerable endpoint, authentication is misconfigured or bypassed, and a theme is installed that can be used as the path parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist-based validation for URI inputs, restricting endpoints to only permitted domains/IPs. Additionally, disable or restrict the upgrade-from-uri theme functionality if not required, and apply the latest security patch from the halo project.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36759 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data