# CVE-2026-12722: Authentication Bypass in FTC Software's E-Commerce Management Panel

> Attackers can bypass authentication to access critical functions in the FTC E-Commerce Management Panel.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-pv5g-5934-fmr2

## What is CVE-2026-12722?

CVE-2026-12722 is a high-severity authentication bypass vulnerability in FTC E-Commerce Management Panel, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing authentication for critical function vulnerability in FTC Software IT Services FTC E-Commerce Management Panel allows Authentication Bypass.

This issue affects FTC E-Commerce Management Panel: before 1.0.2.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-12722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12722 is a high-severity authentication bypass vulnerability in FTC E-Commerce Management Panel, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12722 in the wild and no public exploit code.

Affected product: FTC E-Commerce Management Panel. 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-12722/ (Markdown: https://insights.sbomify.com/CVE-2026-12722/index.md)
```

## Sources

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

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