CVE-2026-2543
Unverified Password Change Vulnerability in vichan Password Handler
Publication date: 2026-02-16
Last updated on: 2026-02-16
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| vichan-devel | vichan | to 5.1.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-640 | The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. |
| CWE-620 | When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-2543 is an authentication bypass vulnerability in vichan-devel vichan up to version 5.1.5, specifically in the Password Change Handler component located in the file inc/mod/pages.php.'}, {'type': 'paragraph', 'content': 'The vulnerability arises because the application allows an authenticated moderator to change their password without verifying the current password. This happens due to reliance on an active session and permission checks without requiring re-authentication or password verification, classified as CWE-620 (Unverified Password Change).'}, {'type': 'paragraph', 'content': "An attacker who gains access to a valid moderator session—via methods such as Cross-Site Scripting (XSS), Cross-Site Request Forgery (CSRF), session fixation, or stolen cookies—can exploit this flaw to change the moderator's password remotely and take over the account."}] [2, 3]
How can this vulnerability impact me? :
This vulnerability impacts the integrity of user accounts by allowing an attacker with access to a valid moderator session to change the password without verification.
Successful exploitation can lead to permanent takeover of moderator accounts, enabling attackers to gain unauthorized control over administrative functions.
The attack can be initiated remotely and is considered easy to exploit once a valid session is obtained, increasing the risk of account compromise.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by identifying if the affected vichan-devel vichan version up to 5.1.5 is in use, specifically by checking for the presence of the vulnerable file inc/mod/pages.php.'}, {'type': 'paragraph', 'content': 'Attackers may use Google dorking techniques such as searching for "inurl:inc/mod/pages.php" to identify vulnerable targets.'}, {'type': 'paragraph', 'content': 'Since the vulnerability involves manipulation of the password change argument without verification, monitoring HTTP requests to the password change handler for suspicious or unauthorized password change attempts could help detect exploitation attempts.'}, {'type': 'paragraph', 'content': 'No specific detection commands are provided in the available resources.'}] [2]
What immediate steps should I take to mitigate this vulnerability?
There are no known countermeasures or mitigations available for this vulnerability.
It is suggested to replace the affected component with an alternative product to avoid the vulnerability.
Since the vulnerability requires an authenticated session, protecting moderator sessions from compromise (e.g., preventing XSS, CSRF, session fixation, and cookie theft) can reduce the risk of exploitation.