CVE-2023-5627 Vulnerability Analysis & Exploit Details

CVE-2023-5627
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2023-5627 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-5627 Details

Status: Modified

Last updated: 🕣 21 Nov 2024, 08:42 UTC
Originally published on: 🕓 01 Nov 2023, 16:15 UTC

Time between publication and last update: 385 days

CVSS Release: version 3

CVSS3 Source

psirt@moxa.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE-2023-5627 Vulnerability Summary

CVE-2023-5627: A vulnerability has been identified in NPort 6000 Series, making the authentication mechanism vulnerable. This vulnerability arises from the incorrect implementation of sensitive information protection, potentially allowing malicious users to gain unauthorized access to the web service.

Assessing the Risk of CVE-2023-5627

Access Complexity Graph

The exploitability of CVE-2023-5627 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-5627

With low attack complexity and no required privileges, CVE-2023-5627 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-5627, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-5627, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2023-5627 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2023-5627 poses no threat to data integrity.
  • Availability: None
    CVE-2023-5627 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.135% (probability of exploit)

EPSS Percentile: 50.29% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 49.71% of others.

CVE-2023-5627 References

External References

CWE Common Weakness Enumeration

CWE-327

CAPEC Common Attack Pattern Enumeration and Classification

  • Encryption Brute Forcing CAPEC-20 An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.
  • Creating a Rogue Certification Authority Certificate CAPEC-459 An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.
  • Signature Spoof CAPEC-473 An attacker generates a message or datablock that causes the recipient to believe that the message or datablock was generated and cryptographically signed by an authoritative or reputable source, misleading a victim or victim operating system into performing malicious actions.
  • Signature Spoofing by Improper Validation CAPEC-475 An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.
  • Cryptanalysis of Cellular Encryption CAPEC-608 The use of cryptanalytic techniques to derive cryptographic keys or otherwise effectively defeat cellular encryption to reveal traffic content. Some cellular encryption algorithms such as A5/1 and A5/2 (specified for GSM use) are known to be vulnerable to such attacks and commercial tools are available to execute these attacks and decrypt mobile phone conversations in real-time. Newer encryption algorithms in use by UMTS and LTE are stronger and currently believed to be less vulnerable to these types of attacks. Note, however, that an attacker with a Cellular Rogue Base Station can force the use of weak cellular encryption even by newer mobile devices.
  • Rooting SIM Cards CAPEC-614 SIM cards are the de facto trust anchor of mobile devices worldwide. The cards protect the mobile identity of subscribers, associate devices with phone numbers, and increasingly store payment credentials, for example in NFC-enabled phones with mobile wallets. This attack leverages over-the-air (OTA) updates deployed via cryptographically-secured SMS messages to deliver executable code to the SIM. By cracking the DES key, an attacker can send properly signed binary SMS messages to a device, which are treated as Java applets and are executed on the SIM. These applets are allowed to send SMS, change voicemail numbers, and query the phone location, among many other predefined functions. These capabilities alone provide plenty of potential for abuse.
  • Cryptanalysis CAPEC-97 Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: Total Break (finding the secret key), Global Deduction (finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key), Information Deduction (gaining some information about plaintexts or ciphertexts that was not previously known) and Distinguishing Algorithm (the attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits).

Vulnerable Configurations

  • cpe:2.3:o:moxa:nport_6150-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6150-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6150-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6150-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6150-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6150-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6150_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6150_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6150_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6150_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6150:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6150:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-m-sc-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-m-sc-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-m-sc-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-m-sc-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6250-m-sc-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6250-m-sc-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-m-sc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-m-sc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-m-sc_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-m-sc_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6250-m-sc:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6250-m-sc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-s-sc-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-s-sc-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-s-sc-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-s-sc-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6250-s-sc-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6250-s-sc-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-s-sc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-s-sc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-s-sc_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-s-sc_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6250-s-sc:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6250-s-sc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6250-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6250-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6250_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6250_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6250:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6250:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6450-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6450-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6450-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6450-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6450-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6450-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6450_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6450_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6450_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6450_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6450:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6450:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-16-48v_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-16-48v_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-16-48v_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-16-48v_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6610-16-48v:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6610-16-48v:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-16_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-16_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-16_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-16_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6610-16:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6610-16:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-32-48v_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-32-48v_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-32-48v_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-32-48v_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6610-32-48v:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6610-32-48v:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-32_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-32_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-32_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-32_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6610-32:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6610-32:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-8-48v_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-8-48v_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-8-48v_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-8-48v_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6610-8-48v:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6610-8-48v:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6610-8_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6610-8_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6610-8:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6610-8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16-48v_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16-48v_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16-48v_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16-48v_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-16-48v:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-16-48v:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16-hv-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16-hv-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16-hv-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16-hv-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-16-hv-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-16-hv-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-16-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-16-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-16_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-16_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-16:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-16:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-32-48v_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-32-48v_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-32-48v_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-32-48v_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-32-48v:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-32-48v:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-32-hv-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-32-hv-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-32-hv-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-32-hv-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-32-hv-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-32-hv-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-32_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-32_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-32_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-32_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-32:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-32:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8-48v_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8-48v_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8-48v_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8-48v_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-8-48v:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-8-48v:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8-hv-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8-hv-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8-hv-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8-hv-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-8-hv-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-8-hv-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8-t_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8-t_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8-t_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8-t_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-8-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-8-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:nport_6650-8_firmware:1.21:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:nport_6650-8_firmware:1.21:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:nport_6650-8:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:nport_6650-8:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-5627: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...