# CVE-2011-4554: Other in n/a

> Authenticated users can inject SMTP commands via crafted organization names or email addresses, potentially manipulating email traffic.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:N/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:** 6 Dec 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w28x-3vhc-vmmg

## What is CVE-2011-4554?

CVE-2011-4554 is a medium-severity vulnerability in n/a, published on 6 Dec 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

One Click Orgs before 1.2.3 allows remote authenticated users to trigger crafted SMTP traffic via (1) " (double quote) and newline characters in an org name or (2) " (double quote) characters in an e-mail address, related to a "2nd Order SMTP Injection" issue.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-4554?

It affects 1 product.


Products: Oneclickorgs One Click Orgs.

## How do I fix CVE-2011-4554?

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

## Is CVE-2011-4554 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4677](https://insights.sbomify.com/CVE-2011-4677/): Information disclosure in n/a (high 7.5)
- [CVE-2011-4553](https://insights.sbomify.com/CVE-2011-4553/): Open redirect in n/a (medium 5.8)
- [CVE-2011-4678](https://insights.sbomify.com/CVE-2011-4678/): Information disclosure in n/a (medium 5.0)
- [CVE-2011-4552](https://insights.sbomify.com/CVE-2011-4552/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2011-4555](https://insights.sbomify.com/CVE-2011-4555/): Business logic in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4554 and fix it if it is affected.

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

## Sources

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

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