CVE-2026-36756
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 /plugins/-/install-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 plugin installation feature at the /plugins/-/install-from-uri endpoint in version v2.22.14. An authenticated attacker can craft malicious GET requests to force the server to make arbitrary HTTP requests to internal resources, enabling internal network scanning and potential access to sensitive internal services.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 Halo CMS installationLocate the Halo CMS installation and determine its version by checking the application startup logs, version file, or administrative dashboard 'About' page.Affected if The installed version is v2.22.14 exactly.
-
Verify plugin installation endpoint existsCheck if the /plugins/-/install-from-uri endpoint is present by reviewing the application routes configuration or attempting a HEAD request to the endpoint (requires authentication).Affected if The endpoint /plugins/-/install-from-uri is accessible and responds to requests.
-
Confirm plugin installation feature is enabledExamine the Halo CMS configuration files (typically halo-config.yaml or application.yml) and the plugin settings in the admin panel to verify the plugin installation feature is not explicitly disabled.Affected if The plugin installation feature is enabled in the configuration.
-
Check authentication requirementsReview the security configuration for the /plugins/-/install-from-uri endpoint to determine if authentication is enforced. In a default v2.22.14 installation, verify whether any user with plugin install permissions can access this endpoint.Affected if The endpoint accepts requests from authenticated users with standard plugin management permissions.
You are affected if running Halo CMS version v2.22.14 with the plugin installation feature and the /plugins/-/install-from-uri endpoint enabled and accessible to authenticated users.
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 dataUpgrade to a patched version of Halo when available. Implement strict URL allowlisting and input validation on the install-from-uri endpoint, and apply network segmentation to restrict outbound requests from the application server.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36756 — 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-36756 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