# CVE-2022-35293: Auth bypass in SAP Enable Now Manager

> Unauthenticated attackers can bypass session management to access user accounts and view or modify data in SAP Enable Now Manager.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 9 Aug 2022
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-333h-f5pr-9xg9

## What is CVE-2022-35293?

CVE-2022-35293 is a critical authentication bypass vulnerability in SAP Enable Now Manager, published on 9 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to insecure session management, SAP Enable Now allows an unauthenticated attacker to gain access to user's account. On successful exploitation, an attacker can view or modify user data causing limited impact on confidentiality and integrity of the application.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-35293?

It affects 1 product.


Products: Sap Enable Now Manager.

## How do I fix CVE-2022-35293?

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

## Is CVE-2022-35293 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35293 and fix it if it is affected.

What it is: CVE-2022-35293 is a critical authentication bypass vulnerability in SAP Enable Now Manager, published on 9 Aug 2022. 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-2022-35293 in the wild and no public exploit code.

Affected product: SAP Enable Now Manager. 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-2022-35293/ (Markdown: https://insights.sbomify.com/CVE-2022-35293/index.md)
```

## Sources

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

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