# CVE-2007-1193: Other in n/a

> Unspecified vulnerabilities in the OrangeHRM login page allow attackers to potentially compromise the system, requiring an upgrade to a patched version.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 2 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h4mg-pjh9-pc8p

## What is CVE-2007-1193?

CVE-2007-1193 is a critical vulnerability in n/a, published on 2 Mar 2007. It can be exploited over the network.

### Official description

Multiple unspecified vulnerabilities in the Login page in OrangeHRM before 20070212 have unknown impact and attack vectors.

## Which versions are affected by CVE-2007-1193?

It affects 1 product.


Products: Orangehrm Orangehrm.

## How do I fix CVE-2007-1193?

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

## Is CVE-2007-1193 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-66224](https://insights.sbomify.com/CVE-2025-66224/): OrangeHRM is Vulnerable to Code Execution Through Arbitrary File Write from Sendmail Parameter Injection (critical 9.0)
- [CVE-2019-12839](https://insights.sbomify.com/CVE-2019-12839/): Command injection in n/a (high 8.8)
- [CVE-2025-66225](https://insights.sbomify.com/CVE-2025-66225/): OrangeHRM is Vulnerable to Account Takeover Through Unvalidated Username in Password Reset Workflow (high 8.7)
- [CVE-2025-66289](https://insights.sbomify.com/CVE-2025-66289/): OrangeHRM is Vulnerable to Persistent Session Access Due to Missing Invalidation After User Disable and Password Change (high 8.7)
- [CVE-2024-36428](https://insights.sbomify.com/CVE-2024-36428/): SQL injection in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1193 and fix it if it is affected.

What it is: CVE-2007-1193 is a critical vulnerability in n/a, published on 2 Mar 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-1193 in the wild and no public exploit code.

Affected product: n/a. 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-2007-1193/ (Markdown: https://insights.sbomify.com/CVE-2007-1193/index.md)
```

## Sources

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

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