# CVE-2026-92932: MISP sachertortephp Xml::build() Operator Precedence Bypass Allows Unintended HTTPS SSRF When readFile Is Disabled

> Attacker can force outbound HTTPS requests bypassing readFile restrictions, enabling internal network access and data disclosure in MISP applications.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-53jr-w5f7-rv64

## What is CVE-2026-92932?

CVE-2026-92932 is a medium-severity server-side request forgery vulnerability in misp sachertortephp, published on 17 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In the MISP sachertortephp library, the Xml::build() static method in lib/Cake/Utility/Xml.php contains a logic error in the conditional that gates network-based XML fetching. The original condition was written as: $options['readFile'] && strpos($input, 'http://') === 0 || strpos($input, 'https://') === 0. Because PHP's && operator has higher precedence than ||, the expression is evaluated as ($options['readFile'] && strpos($input, 'http://') === 0) || strpos($input, 'https://') === 0. As a result, when a caller explicitly sets the readFile option to false to disable file and URL reading, an input string beginning with https:// still satisfies the condition and triggers a network fetch via HttpSocket (configured to follow up to 10 redirects). The http:// branch is correctly gated by the readFile flag, but the https:// branch is not. An attacker who can influence the $input parameter passed to Xml::build() can therefore force the application to issue an outbound HTTPS request to an attacker-controlled or internal URL, even though the caller intended to suppress all remote reads. The fetched response is parsed as XML and may be returned to the caller, enabling information disclosure from internal services or external targets. This constitutes a Server-Side Request Forgery (SSRF) weakness with an information-disclosure impact. The vulnerability requires that the code path in Xml::build() be reachable with attacker-controlled input and that the readFile option be set to false (or the caller expects it to be false).

Weakness: CWE-918 (Server-Side Request Forgery), CWE-670 (Always-Incorrect Control Flow Implementation)

## Which versions are affected by CVE-2026-92932?


## How do I fix CVE-2026-92932?

No fix has been published for CVE-2026-92932 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92932 being exploited?

There is no known exploitation of CVE-2026-92932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92932 and fix it if it is affected.

What it is: CVE-2026-92932 is a medium-severity server-side request forgery vulnerability in misp sachertortephp, published on 17 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92932 in the wild and no public exploit code.

Affected product: misp sachertortephp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92932/ (Markdown: https://insights.sbomify.com/CVE-2026-92932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92932
- OSV: https://osv.dev/vulnerability/CVE-2026-92932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92932/
Summaries are generated and may contain mistakes; the official description above is the record.