VulnerabilityPublished 12 Jun 2024Updated 13 Sep 2024

CVE-2024-36523: Wvp GB28181 Pro · Insufficient Session Expiration

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Until an official patch is released, organizations should implement several specific mitigations: 1) Enforce immediate session termination upon account deletion by manually invalidating active sessions or tokens through administrative controls or backend database operations. 2) Restrict account deletion privileges to highly trusted administrators to minimize the risk of abuse. 3) Implement monitoring and alerting for unusual access patterns from accounts marked for deletion. 4) Encourage users to log out immediately after deleting accounts to prevent continued access. 5) Review and enhance session management policies to ensure tokens are invalidated on account status changes. 6) If possible, deploy network-level access controls to limit exposure of the application to trusted networks only. 7) Stay alert for vendor updates or patches addressing this vulnerability and apply them promptly. These measures go beyond generic advice by focusing on session lifecycle management and administrative controls specific to this vulnerability.

Description

An access control issue in Wvp GB28181 Pro 2.0 allows users to continue to access information in the application after deleting their own or administrator accounts. This is provided that the users do not log out of their deleted accounts.

Impact

The primary impact of this vulnerability is unauthorized access to sensitive information within the Wvp GB28181 Pro 2.0 application after account deletion. Attackers or users who delete their accounts but maintain active sessions can continue to view or extract confidential data, potentially including video feeds, user information, or system configurations. This compromises confidentiality and could lead to data leakage or privacy violations. Since the vulnerability does not affect data integrity or system availability, the risk is limited to information exposure. However, given the use of GB28181 in surveillance and security systems, unauthorized access could have serious operational and privacy consequences. Organizations relying on this software for critical monitoring or security functions may face compliance issues and reputational damage if sensitive data is exposed. The lack of patches and known exploits suggests the threat is currently theoretical but could become practical if attackers develop exploits or insiders abuse the flaw.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/648540858/wvp-GB28181-pro/issues/1456 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 03:26 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats