# CVE-2025-24337: Insecure default config access in WriteFreely

> Local attackers can read the config.ini file to discover MySQL database credentials in WriteFreely installations.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jan 2025
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-3qc3-mx6x-267h, GO-2025-3410

## What is CVE-2025-24337?

CVE-2025-24337 is a high-severity vulnerability in Musing Studio WriteFreely, published on 20 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WriteFreely through 0.15.1, when MySQL is used, allows local users to discover credentials by reading config.ini.

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2025-24337?

3 open source packages ship an affected version, including github.com/writefreely/writefreely.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/writefreely/writefreely` | Go | All versions | None |
| `github.com/writefreely/writefreely` | Go | All versions to 0.15.1 | None |
| `github.com/writefreely/writefreely` | Go | All versions to 0.15.1 | None |

## How do I fix CVE-2025-24337?

Upgrade to a fixed version.

## Is CVE-2025-24337 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24337 and fix it if it is affected.

What it is: CVE-2025-24337 is a high-severity vulnerability in Musing Studio WriteFreely, published on 20 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24337 exists.

Affected packages and fixed versions:
- github.com/writefreely/writefreely (Go): affected all versions; no fix listed
- github.com/writefreely/writefreely (Go): affected all versions up to 0.15.1; no fix listed
- github.com/writefreely/writefreely (Go): affected all versions up to 0.15.1; 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-2025-24337/ (Markdown: https://insights.sbomify.com/CVE-2025-24337/index.md)
```

## Sources

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

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