CVE-2025-8554
BaseFortify
Publication date: 2025-08-05
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pybbs_project | pybbs | to 6.0.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8554 is a reflected Cross-Site Scripting (XSS) vulnerability in the atjiu pybbs application up to version 6.0.0. It occurs in the /admin/user/list endpoint where the 'username' parameter is not properly encoded before being displayed on the page. This allows an attacker to inject malicious scripts that execute in the context of administrator users who view this page, potentially compromising their sessions or actions. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to execute malicious scripts in the context of administrator users. This can lead to compromised administrative sessions, unauthorized actions performed by attackers, and potential data integrity issues. Exploitation requires some user interaction and authentication but can be initiated remotely, making it a risk for administrative control and security. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/user/list endpoint for reflected cross-site scripting (XSS) via the 'username' parameter. You can use tools like curl or a web proxy to send requests with XSS payloads and observe if the payload is reflected unencoded in the response. For example, a command using curl might be: curl -G 'http://yourserver/admin/user/list' --data-urlencode 'username=<script>alert(1)</script>' If the response contains the script tag unencoded, the vulnerability is present. Additionally, automated scanners that test for reflected XSS can be used against this endpoint. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to apply the available patch identified by commit 2fe4a51afbce0068c291bc1818bbc8f7f3b01a22. This patch properly encodes the 'username' parameter output in the /admin/user/list endpoint to prevent reflected XSS. Until the patch is applied, restrict access to the /admin/user/list endpoint to trusted administrators only and consider using web application firewalls (WAF) to block suspicious input patterns targeting the 'username' parameter. [3]