MeWare PDKS prior MYR_3.5.2025117 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.6$0-$5k0.00

Summaryinfo

A vulnerability was found in MeWare PDKS and classified as problematic. This vulnerability affects unknown code. Such manipulation leads to improper control of interaction frequency. This vulnerability is listed as CVE-2026-7402. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in MeWare PDKS. Affected by this issue is an unknown code. 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. CVE summarizes:

Improper Control of Interaction Frequency vulnerability in MeWare Software Development Inc. PDKS allows Flooding. This issue affects PDKS: from V16.20200313 before VMYR_3.5.2025117.

The weakness was presented by Berat Akşi̇t. The advisory is shared for download at usom.gov.tr. This vulnerability is handled as CVE-2026-7402 since 04/29/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available.

Upgrading to version MYR_3.5.2025117 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.7
VulDB Meta Temp Score: 6.6

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

CNA Base Score: 8.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

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: PDKS MYR_3.5.2025117

Timelineinfo

04/29/2026 CVE reserved
04/30/2026 +1 days Advisory disclosed
04/30/2026 +0 days VulDB entry created
04/30/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: usom.gov.tr
Researcher: Berat Akşi̇t
Status: Confirmed

CVE: CVE-2026-7402 (🔒)
GCVE (CVE): GCVE-0-2026-7402
GCVE (VulDB): GCVE-100-360308

Entryinfo

Created: 04/30/2026 16:29
Changes: 04/30/2026 16:29 (62)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!