# CVE-2023-5318: Use of Hard-coded Credentials in microweber/microweber

> Attackers can exploit hard-coded credentials in Microweber to gain unauthorized access and potentially take over accounts or read data.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/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:** 30 Sep 2023
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-r657-3wqh-g2x9

## What is CVE-2023-5318?

CVE-2023-5318 is a medium-severity vulnerability in Microweber Microweber, published on 30 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of Hard-coded Credentials in GitHub repository microweber/microweber prior to 2.0.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

2 open source packages ship an affected version, including microweber/microweber. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `microweber/microweber` | Packagist | All versions to 1.3.4 | None |
| `microweber/microweber` | Packagist | All versions to 1.3.4 | None |

Products: Microweber Microweber.

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

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

## Is CVE-2023-5318 being exploited?

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

## Other vulnerabilities in Microweber Microweber

- [CVE-2022-0558](https://insights.sbomify.com/CVE-2022-0558/): Cross-site Scripting (XSS) - Stored in microweber/microweber (critical 9.8)
- [CVE-2020-23138](https://insights.sbomify.com/CVE-2020-23138/): File upload in n/a (critical 9.8)
- [CVE-2022-0688](https://insights.sbomify.com/CVE-2022-0688/): Business Logic Errors in microweber/microweber (critical 9.4)
- [CVE-2022-0660](https://insights.sbomify.com/CVE-2022-0660/): Generation of Error Message Containing Sensitive Information in microweber/microweber (critical 9.4)
- [CVE-2022-0913](https://insights.sbomify.com/CVE-2022-0913/): Integer Overflow or Wraparound in microweber/microweber (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5318 is a medium-severity vulnerability in Microweber Microweber, published on 30 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5318 exists.

Affected packages and fixed versions:
- microweber/microweber (Packagist): affected all versions up to 1.3.4; no fix listed
- microweber/microweber (Packagist): affected all versions up to 1.3.4; no fix listed

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-5318/ (Markdown: https://insights.sbomify.com/CVE-2023-5318/index.md)
```

## Sources

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

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