# CVE-2010-1238: Security feature bypass in n/a

> Remote attackers can bypass textcha protection in MoinMoin by submitting empty fields, allowing automated spam or abuse.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 5 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qwwp-27qm-g533

## What is CVE-2010-1238?

CVE-2010-1238 is a medium-severity vulnerability in n/a, published on 5 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MoinMoin 1.7.1 allows remote attackers to bypass the textcha protection mechanism by modifying the textcha-question and textcha-answer fields to have empty values.

Weakness: CWE-264

## Which versions are affected by CVE-2010-1238?

It affects 1 product.


Products: Moinmo Moinmoin.

## How do I fix CVE-2010-1238?

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

## Is CVE-2010-1238 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15275](https://insights.sbomify.com/CVE-2020-15275/): malicious SVG attachment causing stored XSS vulnerability in MoinMoin (high 8.7)
- [CVE-2009-4762](https://insights.sbomify.com/CVE-2009-4762/): MoinMoin Improper Access Control vulnerability (high 7.5)
- [CVE-2010-0669](https://insights.sbomify.com/CVE-2010-0669/): MoinMoin improper sanitizes user profiles (high 7.5)
- [CVE-2010-0717](https://insights.sbomify.com/CVE-2010-0717/): MoinMoin has improper default configuration (high 7.5)
- [CVE-2010-0668](https://insights.sbomify.com/CVE-2010-0668/): MoinMoin has multiple vulnerabilities related to superuser list, xmlrpc and OpenID configuration (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1238 and fix it if it is affected.

What it is: CVE-2010-1238 is a medium-severity vulnerability in n/a, published on 5 Apr 2010. 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-2010-1238 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-2010-1238/ (Markdown: https://insights.sbomify.com/CVE-2010-1238/index.md)
```

## Sources

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

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