VulnerabilityPublished 24 Jan 2024Updated 30 May 2025

CVE-2023-43991

Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% 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:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 24 Jan 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

Organizations should immediately audit and secure their channel access tokens by implementing strict access controls and rotating tokens regularly to limit exposure time. Monitoring and logging of token usage should be enhanced to detect anomalous notification activity. Developers should review the mini-app’s code and integration points to ensure tokens are not exposed in logs, URLs, or client-side storage. Applying the principle of least privilege to tokens and restricting their scope can reduce potential damage if leaked. User awareness campaigns can help mitigate the impact of malicious notifications by educating users to recognize suspicious messages. Finally, coordination with Line platform support and monitoring for vendor advisories or patches is essential for timely remediation.

Description

An issue in PRIMA CLINIC mini-app on Line v13.6.1 allows attackers to send crafted malicious notifications via leakage of the channel access token.

Impact

For European organizations, especially those using the Line platform or integrating the PRIMA CLINIC mini-app for healthcare or communication services, this vulnerability poses a risk of unauthorized message injection. This can lead to targeted phishing campaigns, social engineering attacks, or dissemination of false information, potentially undermining trust in digital communication channels. Healthcare providers or clinics using this mini-app could face reputational damage and regulatory scrutiny under GDPR if personal data is indirectly exposed or manipulated. The unauthorized notifications could also disrupt patient communication workflows or cause confusion, impacting service delivery. Since the vulnerability requires leakage of the channel access token, organizations with weak token management or insufficient access controls are at higher risk. The medium severity suggests a moderate but tangible threat that should be addressed promptly to prevent escalation or exploitation in conjunction with other vulnerabilities.

References

github.com/syz913/CVE-reports/blob/main/CVE-2023-43991.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 19:25 UTC

Technical details

References

Community reviews

Related threats