MIA Pizzy Library prior 1.3.9.26250 improper control of interaction frequency

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.1$0-$5k5.38

Summaryinfo

A vulnerability identified as problematic has been detected in MIA Pizzy Library. Impacted is an unknown function. The manipulation leads to improper control of interaction frequency. This vulnerability is referenced as CVE-2026-5233. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in MIA Pizzy Library. It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a improper control of interaction frequency vulnerability. Using CWE to declare the problem leads to CWE-799. The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests. Impacted is integrity, and availability. The summary by CVE is:

Improper Control of Interaction Frequency vulnerability in MIA Technology Inc. Pizzy Library allows Flooding. This issue affects Pizzy Library: from 1.0.0.26250 before 1.3.9.26250.

The weakness was published by Ahmet Durmuş. The advisory is shared at siberguvenlik.gov.tr. The identification of this vulnerability is CVE-2026-5233 since 03/31/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.3.9.26250 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.2
VulDB Meta Temp Score: 6.1

VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.1
CNA Vector (TR-CERT): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper control of interaction frequency
CWE: CWE-799 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Pizzy Library 1.3.9.26250

Timelineinfo

03/31/2026 CVE reserved
06/15/2026 +76 days Advisory disclosed
06/15/2026 +0 days VulDB entry created
06/15/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: siberguvenlik.gov.tr
Researcher: Ahmet Durmuş
Status: Confirmed

CVE: CVE-2026-5233 (🔒)
GCVE (CVE): GCVE-0-2026-5233
GCVE (VulDB): GCVE-100-370925

Entryinfo

Created: 06/15/2026 16:58
Changes: 06/15/2026 16:58 (63)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!