Unauthenticated content publishing via missing login check
Published Mar 30, 2022 · Updated Aug 4, 2024
Missing authorization in NexusPHP 1.5 allows remote attackers to publish Funbox content through the unauthenticated fun.php endpoint. The add action accepts subject and body fields and stores a post without checking for a logged-in user, leaving the publisher empty. Network access to the site is sufficient; the injected post is displayed on the home page to all users, subject to one post per 24 hours.
Summary
What happened
Missing authorization in NexusPHP 1.5 allows remote attackers to publish Funbox content through the unauthenticated fun.php endpoint. The add action accepts subject and body fields and stores a post without checking for a logged-in user, leaving the publisher empty. Network access to the site is sufficient; the injected post is displayed on the home page to all users, subject to one post per 24 hours.
The record
- CVE
- CVE-2020-24771
- Published
- Mar 30, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 30, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Unauthenticated Funbox publishing requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo