# CVE-2004-1982: Other in n/a

> Remote attackers can modify forum records by injecting carriage returns into the subject field, requiring 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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pqm2-r3mv-x23f

## What is CVE-2004-1982?

CVE-2004-1982 is a medium-severity vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Post.pl in YaBB 1 Gold SP 1.2 allows remote attackers to modify records in the board's .txt file via carriage return characters in the subject field.

## Which versions are affected by CVE-2004-1982?

It affects 1 product.


Products: Yabb Yabb.

## How do I fix CVE-2004-1982?

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

## Is CVE-2004-1982 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3208](https://insights.sbomify.com/CVE-2007-3208/): Other in n/a (critical 10.0)
- [CVE-2004-2403](https://insights.sbomify.com/CVE-2004-2403/): Cross-site request forgery in n/a (critical 10.0)
- [CVE-2004-0343](https://insights.sbomify.com/CVE-2004-0343/): SQL injection in n/a (critical 10.0)
- [CVE-2013-2057](https://insights.sbomify.com/CVE-2013-2057/): Path traversal in YaBB (critical 9.8)
- [CVE-2006-3275](https://insights.sbomify.com/CVE-2006-3275/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1982 and fix it if it is affected.

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

## Sources

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

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