# CVE-2007-2591: Missing authorization in n/a

> Remote attackers can modify user account details and deactivate accounts via the userid parameter in Nokia Intellisync Mobile Suite.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5r33-5w5f-f47j

## What is CVE-2007-2591?

CVE-2007-2591 is a high-severity missing authorization vulnerability in n/a, published on 11 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

usrmgr/userList.asp in Nokia Intellisync Mobile Suite 6.4.31.2, 6.6.0.107, and 6.6.2.2, possibly involving Novell Groupwise Mobile Server and Nokia Intellisync Wireless Email Express, allows remote attackers to modify user account details and cause a denial of service (account deactivation) via the userid parameter in an update action.

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

It affects 3 products.


Products: Nokia Groupwise Mobile Server, Nokia Intellisync Mobile Suite, Nokia Intellisync Wireless Email Express.

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

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

## Is CVE-2007-2591 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2590](https://insights.sbomify.com/CVE-2007-2590/): Information disclosure in n/a (medium 6.4)
- [CVE-2007-2592](https://insights.sbomify.com/CVE-2007-2592/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2591 is a high-severity missing authorization vulnerability in n/a, published on 11 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2591 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-2591/ (Markdown: https://insights.sbomify.com/CVE-2007-2591/index.md)
```

## Sources

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

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