# CVE-2024-9108: Wechat Social login <= 1.3.0 - Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files via the Wechat Social login plugin, potentially leading to remote code execution on the server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3xpv-gvv8-7m5h

## What is CVE-2024-9108?

CVE-2024-9108 is a critical vulnerability in xunhuweb Wechat Social login 微信QQ钉钉登录插件, published on 1 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Wechat Social login plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'convert_remoteimage_to_local' function in versions up to, and including, 1.3.0. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-9108?


## How do I fix CVE-2024-9108?

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

## Is CVE-2024-9108 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9108 and fix it if it is affected.

What it is: CVE-2024-9108 is a critical vulnerability in xunhuweb Wechat Social login 微信QQ钉钉登录插件, published on 1 Oct 2024. 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-2024-9108 in the wild and no public exploit code.

Affected product: xunhuweb Wechat Social login 微信QQ钉钉登录插件. 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-2024-9108/ (Markdown: https://insights.sbomify.com/CVE-2024-9108/index.md)
```

## Sources

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

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