CVE-2026-21429
Permission Bypass in Emlog 2.5.23 Restricts Article Editing
Publication date: 2026-01-02
Last updated on: 2026-04-29
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| emlog | emlog | 2.5.23 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-21429 is a Broken Access Control vulnerability in emlog version 2.5.23. Although the admin can set controls to prevent users from editing or deleting their articles after publishing, a registered user can bypass these restrictions by intercepting and modifying the HTTP request used to update an article. This allows unauthorized editing of article content despite the admin's settings. [1]
How can this vulnerability impact me? :
This vulnerability allows registered users to bypass restrictions and modify their published articles without authorization. This can lead to unauthorized content changes, potentially undermining content integrity and trustworthiness on the website. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring HTTP requests related to article editing in emlog version 2.5.23. Specifically, intercept and analyze HTTP requests from registered users attempting to edit or delete published articles. Tools like Burp Suite can be used to intercept and modify these requests to test if unauthorized edits are possible despite admin restrictions. There are no specific commands provided, but using an HTTP proxy/interceptor tool to capture and modify requests is the suggested approach. [1]
What immediate steps should I take to mitigate this vulnerability?
Since no patched versions are available, immediate mitigation steps include restricting registered user permissions carefully, monitoring and logging article edit requests for suspicious activity, and possibly disabling article editing features for registered users until a fix is released. Additionally, using web application firewalls (WAF) to detect and block tampered HTTP requests may help reduce exploitation risk. [1]