# CVE-2010-4728: Weak cryptography in n/a

> Remote attackers can predict random values to bypass authentication mechanisms in Zikula CMS due to weak random number generation.

- **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:** 8 Feb 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wf9j-wrqc-3h9g

## What is CVE-2010-4728?

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

### Official description

Zikula before 1.3.1 uses the rand and srand PHP functions for random number generation, which makes it easier for remote attackers to defeat protection mechanisms based on randomization by predicting a return value, as demonstrated by the authid protection mechanism.

Weakness: CWE-310

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

It affects 1 product.


Products: Zikula Zikula Application Framework.

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

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

## Is CVE-2010-4728 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2293](https://insights.sbomify.com/CVE-2014-2293/): Deserialization in n/a (critical 9.8)
- [CVE-2016-9835](https://insights.sbomify.com/CVE-2016-9835/): Deserialization in n/a (critical 9.8)
- [CVE-2010-4729](https://insights.sbomify.com/CVE-2010-4729/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-0535](https://insights.sbomify.com/CVE-2011-0535/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2010-1732](https://insights.sbomify.com/CVE-2010-1732/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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