# CVE-2025-8549: atjiu pybbs UserAdminController.java update weak password

> Weak password requirements in the admin user update function allow attackers to set easily guessable passwords, potentially leading to account takeover.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 5 Aug 2025
- **Also known as:** GHSA-p4f9-7f2f-g69h

## What is CVE-2025-8549?

CVE-2025-8549 is a medium-severity vulnerability in atjiu pybbs, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in atjiu pybbs up to 6.0.0. It has been classified as critical. Affected is the function update of the file src/main/java/co/yiiu/pybbs/controller/admin/UserAdminController.java. The manipulation leads to weak password requirements. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The patch is identified as d09cb19a8e7d7e5151282926ada54080244d499f. It is recommended to apply a patch to fix this issue.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Pybbs Project Pybbs.

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

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

## Is CVE-2025-8549 being exploited?

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

## Other vulnerabilities in atjiu pybbs

- [CVE-2020-28702](https://insights.sbomify.com/CVE-2020-28702/): SQL injection in n/a (high 7.5)
- [CVE-2025-8546](https://insights.sbomify.com/CVE-2025-8546/): atjiu pybbs Verification Code login Captcha (medium 6.9)
- [CVE-2025-8547](https://insights.sbomify.com/CVE-2025-8547/): atjiu pybbs Email Verification improper authorization (medium 6.9)
- [CVE-2025-8548](https://insights.sbomify.com/CVE-2025-8548/): atjiu pybbs Registered Email SettingsApiController.java sendEmailCode information exposure (medium 6.3)
- [CVE-2022-23391](https://insights.sbomify.com/CVE-2022-23391/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8549 is a medium-severity vulnerability in atjiu pybbs, published on 5 Aug 2025. 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-2025-8549 exists.

Affected product: atjiu pybbs. 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-2025-8549/ (Markdown: https://insights.sbomify.com/CVE-2025-8549/index.md)
```

## Sources

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

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