Home
» Security vulnerabilities
» CVE-2023-4454
Cross-Site Request Forgery (CSRF) in GitHub repository wallabag/wallabag prior to 2.6.3.
NVD Status: Modified ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2023-4454
Conclusion & alert: CVE-2023-4454 is rated Exploit Available (50/100) : CVSS Medium severity, with low exploitation likelihood (EPSS 0.14%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Public exploit references (Exploit-DB) for CVE-2023-4454
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2023-4454
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-03-15
0.15%
0.14%
-0.01%
2
2025-11-21
0.09%
0.15%
+0.06%
3
2025-11-18
—
0.09%
—
Full EPSS history
(6 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2023-4454
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
5.7
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.1
3.6
[email protected]
4.3
3.0
MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
1.4
[email protected]
Weakness enumeration for CVE-2023-4454
GitHub Security Advisory for CVE-2023-4454
GHSA-p8gp-899c-jvq9 · Severity: medium · Ecosystem: composer
— Wallabag user can reset data unintentionally
Affected software / configurations for CVE-2023-4454
Vendor
Product
Version
Raw CPE
wallabag
wallabag
< 2.6.3
cpe:2.3:a:wallabag:wallabag:*:*:*:*:*:*:*:*
References for CVE-2023-4454
cvelogic
Threat Intelligence