flask-dashboard Flask-MonitoringDashboard up to 5.0.2 cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 2.35+ |
Summary
A vulnerability has been found in flask-dashboard Flask-MonitoringDashboard up to 5.0.2 and classified as problematic. This affects an unknown part. Performing a manipulation results in cross-site request forgery. This vulnerability is known as CVE-2026-15034. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability classified as problematic has been found in flask-dashboard Flask-MonitoringDashboard up to 5.0.2. This affects an unknown part. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-15034. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/08/2026 Advisory disclosed07/08/2026 VulDB entry created
07/08/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 557
Status: Not defined
CVE: CVE-2026-15034 (🔒)
GCVE (CVE): GCVE-0-2026-15034
GCVE (VulDB): GCVE-100-376785
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/08/2026 09:43Changes: 07/08/2026 09:43 (56)
Complete: 🔍
Submitter: flashzyc
Cache ID: 216::103
Submit
Accepted
- Submit #850877: flask-dashboard Flask-MonitoringDashboard v5.0.2 CSRF (by flashzyc)
Duplicate
- Submit #XXXXXX: Xxxxx-xxxxxxxxx Xxxxx-xxxxxxxxxxxxxxxxxxx Xx.x.x Xxxx (by flashzyc)
- Submit #XXXXXX: Xxxxx-xxxxxxxxx Xxxxx-xxxxxxxxxxxxxxxxxxx Xx.x.x Xxxx (by flashzyc)
- Submit #XXXXXX: Xxxxx-xxxxxxxxx Xxxxx-xxxxxxxxxxxxxxxxxxx Xx.x.x Xxxx (by flashzyc)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.