# CVE-2025-67650: Authenticated SQL Injection in PHP Jabbers scripts

> Authenticated attackers can exploit SQL injection in sorting parameters of PHP Jabbers scripts to read or modify database contents.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-h3q5-7qh5-pg2p

## What is CVE-2025-67650?

CVE-2025-67650 is a high-severity SQL injection vulnerability in PHP Jabbers Appointment Scheduler, published on 31 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated SQL injection vulnerability has been identified in multiple PHP Jabbers scripts. Improper neutralization of input provided by an authenticated user into parameters responsible for sorting functions allows an attacker to perform SQL Injection attacks.
This issue was fixed in the versions specified in the affected products list.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-67650?


## How do I fix CVE-2025-67650?

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

## Is CVE-2025-67650 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67650 and fix it if it is affected.

What it is: CVE-2025-67650 is a high-severity SQL injection vulnerability in PHP Jabbers Appointment Scheduler, published on 31 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67650 in the wild and no public exploit code.

Affected product: PHP Jabbers Appointment Scheduler. 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-2025-67650/ (Markdown: https://insights.sbomify.com/CVE-2025-67650/index.md)
```

## Sources

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

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