# CVE-2023-3849: mooSocial mooDating URL find-a-match cross site scripting

> Remote attackers can inject malicious scripts via the find-a-match URL handler in mooSocial mooDating, potentially compromising user sessions.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jul 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-497v-f99c-488c

## What is CVE-2023-3849?

CVE-2023-3849 is a low-severity cross-site scripting vulnerability in mooSocial mooDating, published on 23 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in mooSocial mooDating 1.2. Affected is an unknown function of the file /find-a-match of the component URL Handler. The manipulation leads to cross site scripting. It is possible to launch the attack remotely. The identifier of this vulnerability is VDB-235200. NOTE: We tried to contact the vendor early about the disclosure but the official mail address was not working properly.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-3849?

It affects 1 product.


Products: Moosocial Moodating.

## How do I fix CVE-2023-3849?

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

## Is CVE-2023-3849 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3849 exists.

Public exploit code:

- mooDating 1.2 - Reflected Cross-site scripting (XSS) (exploitdb)
- mooDating 1.2 - Cross-site scripting (nuclei): http/cves/2023/CVE-2023-3849.yaml

## Other vulnerabilities in mooSocial mooDating

- [CVE-2023-3843](https://insights.sbomify.com/CVE-2023-3843/): mooSocial mooDating URL question cross site scripting (low 3.5)
- [CVE-2023-3844](https://insights.sbomify.com/CVE-2023-3844/): mooSocial mooDating URL friends cross site scripting (low 3.5)
- [CVE-2023-3845](https://insights.sbomify.com/CVE-2023-3845/): mooSocial mooDating URL ajax_invite cross site scripting (low 3.5)
- [CVE-2023-3846](https://insights.sbomify.com/CVE-2023-3846/): mooSocial mooDating URL pages cross site scripting (low 3.5)
- [CVE-2023-3847](https://insights.sbomify.com/CVE-2023-3847/): mooSocial mooDating URL users cross site scripting (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3849 and fix it if it is affected.

What it is: CVE-2023-3849 is a low-severity cross-site scripting vulnerability in mooSocial mooDating, published on 23 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3849 exists.

Affected product: mooSocial mooDating. 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-2023-3849/ (Markdown: https://insights.sbomify.com/CVE-2023-3849/index.md)
```

## Sources

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

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