How severe is CVE-2023-31818?

CVE-2023-31818 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2023-31818 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-31818?

CVE-2023-31818 affects Marukyu Marukyu Line. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-31818?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2023-31818 published?

CVE-2023-31818 was published on 2023-07-11 and last updated on 2026-07-09.

CVE-2023-31818

CVE-2023-31818 is a high-severity vulnerability in Marukyu Marukyu Line with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-668.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 1% (52nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-668
Affected product: Marukyu Marukyu Line
Published: 2023-07-11
Last modified: 2026-07-09

Description

An issue found in Marukyu Line v.13.4.1 allows a remote attacker to gain access to sensitive information via the channel access token in the miniapp function.

Frequently asked questions

What is CVE-2023-31818?: An issue found in Marukyu Line v.13.4.1 allows a remote attacker to gain access to sensitive information via the channel access token in the miniapp function.
How severe is CVE-2023-31818?: CVE-2023-31818 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2023-31818 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-31818?: CVE-2023-31818 affects Marukyu Marukyu Line. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-31818?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2023-31818 published?: CVE-2023-31818 was published on 2023-07-11 and last updated on 2026-07-09.

References

https://github.com/syz913/CVE-reports/blob/main/CVE-2023-31818.md

Affected products (1)

cpe:2.3:a:marukyu:marukyu_line:13.4.1:*:*:*:*:*:*:*

Other CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities

CVE-2025-2857 — Critical (CVSS 10.0): Following the recent Chrome sandbox escape (CVE-2025-2783), various Firefox developers identified a similar pattern in…
CVE-2019-8779 — Critical (CVSS 10.0): A logic issue applied the incorrect restrictions. This issue was addressed by updating the logic to apply the correct…
CVE-2012-1846 — Critical (CVSS 10.0): Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the sandbox protection mechanism by leveraging…
CVE-2022-43684 — Critical (CVSS 9.9): ServiceNow has released patches and an upgrade that address an Access Control List (ACL) bypass issue in ServiceNow…
CVE-2022-24900 — Critical (CVSS 9.9): Piano LED Visualizer is software that allows LED lights to light up as a person plays a piano connected to a computer.…
CVE-2019-16541 — Critical (CVSS 9.9): Jenkins JIRA Plugin 3.0.10 and earlier does not declare the correct (folder) scope for per-folder Jira site…

Browse all CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities →