# CVE-2026-88825: iGMS Direct Booking < 2.0 - Unauthenticated Stored XSS via Widget Settings

> Unauthenticated attackers can inject malicious scripts into widget settings, leading to code execution and potential account takeover when administrators or visitors view the widget.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-mhm7-gh54-p5xg

## What is CVE-2026-88825?

CVE-2026-88825 is a high-severity cross-site scripting vulnerability in Unknown iGMS Direct Booking, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The iGMS Direct Booking WordPress plugin before 2.0 does not authorise or escape its widget appearance settings, allowing unauthenticated users to store arbitrary web scripts that execute in the context of an administrator viewing the iGMS Direct Booking WordPress plugin before 2.0 settings, and in the browser of any visitor to a page displaying the booking widget.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-88825 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88825 is a high-severity cross-site scripting vulnerability in Unknown iGMS Direct Booking, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-88825 in the wild and no public exploit code.

Affected product: Unknown iGMS Direct Booking. 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-88825/ (Markdown: https://insights.sbomify.com/CVE-2026-88825/index.md)
```

## Sources

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

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