# CVE-2005-1817: Missing authorization in n/a

> Remote attackers can edit arbitrary forum posts in Invision Power Board by sending modified parameters to index.php, requiring only low privileges.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **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:** 1 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qccv-8vqh-r66h

## What is CVE-2005-1817?

CVE-2005-1817 is a medium-severity missing authorization vulnerability in n/a, published on 1 Jun 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Invision Power Board (IPB) 1.0 through 1.3 allows remote attackers to edit arbitrary forum posts via a direct request to index.php with modified parameters.

## Which versions are affected by CVE-2005-1817?

It affects 1 product.


Products: Invision Power Services Invision Board.

## How do I fix CVE-2005-1817?

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

## Is CVE-2005-1817 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1817 exists.

Public exploit code:

- Invision Power Board 1.x - Unauthorized Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0338](https://insights.sbomify.com/CVE-2004-0338/): SQL injection in n/a (critical 10.0)
- [CVE-2006-3544](https://insights.sbomify.com/CVE-2006-3544/): SQL injection in n/a (high 7.5)
- [CVE-2005-1598](https://insights.sbomify.com/CVE-2005-1598/): SQL injection in n/a (high 7.5)
- [CVE-2004-1785](https://insights.sbomify.com/CVE-2004-1785/): SQL injection in n/a (high 7.5)
- [CVE-2005-1070](https://insights.sbomify.com/CVE-2005-1070/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1817 and fix it if it is affected.

What it is: CVE-2005-1817 is a medium-severity missing authorization vulnerability in n/a, published on 1 Jun 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1817 exists.

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-2005-1817/ (Markdown: https://insights.sbomify.com/CVE-2005-1817/index.md)
```

## Sources

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

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