# CVE-2010-1916: Auth bypass in n/a

> Remote attackers can bypass access restrictions to modify plugin configurations and potentially execute arbitrary code via crafted parameters in the Xinha WYSIWYG editor.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w8pf-76j7-6h39

## What is CVE-2010-1916?

CVE-2010-1916 is a high-severity authentication bypass vulnerability in S9y Serendipity, published on 12 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The dynamic configuration feature in Xinha WYSIWYG editor 0.96 Beta 2 and earlier, as used in Serendipity 1.5.2 and earlier, allows remote attackers to bypass intended access restrictions and modify the configuration of arbitrary plugins via (1) crafted backend_config_secret_key_location and backend_config_hash parameters that are used in a SHA1 hash of a shared secret that can be known or externally influenced, which are not properly handled by the "Deprecated config passing" feature; or (2) crafted backend_data and backend_data[key_location] variables, which are not properly handled by the xinha_read_passed_data function.  NOTE: this can be leveraged to upload and possibly execute arbitrary files via config.inc.php in the ImageManager plugin.

Weakness: CWE-264

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

It affects 2 products.


Products: S9y Serendipity, Xinha Wysiwyg Editor.

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

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

## Is CVE-2010-1916 being exploited?

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

## Other vulnerabilities in S9y Serendipity

- [CVE-2005-1449](https://insights.sbomify.com/CVE-2005-1449/): Other in n/a (critical 10.0)
- [CVE-2005-1452](https://insights.sbomify.com/CVE-2005-1452/): Missing authorization in n/a (critical 10.0)
- [CVE-2020-10964](https://insights.sbomify.com/CVE-2020-10964/): File upload in n/a (critical 9.8)
- [CVE-2011-1134](https://insights.sbomify.com/CVE-2011-1134/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2016-10752](https://insights.sbomify.com/CVE-2016-10752/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-1916 is a high-severity authentication bypass vulnerability in S9y Serendipity, published on 12 May 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-1916 in the wild and no public exploit code.

Affected product: S9y Serendipity. 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-1916/ (Markdown: https://insights.sbomify.com/CVE-2010-1916/index.md)
```

## Sources

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

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