Home
» Security vulnerabilities
» CVE-2023-1541
Business Logic Errors in GitHub repository answerdev/answer prior to 1.0.6.
NVD Status: Modified ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2023-1541
Conclusion & alert: CVE-2023-1541 is rated Exploit Available (50/100) : CVSS Low severity, with low exploitation likelihood (EPSS 0.64%). 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-1541
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2023-1541
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-06-15
0.31%
0.64%
+0.33%
2
2026-05-16
0.41%
0.31%
-0.09%
3
2026-03-22
—
0.41%
—
Full EPSS history
(11 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2023-1541
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
3.8
3.1
LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L
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:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
1.2
2.5
[email protected]
6.0
3.0
MEDIUM
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H
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:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.2
4.7
[email protected]
Weakness enumeration for CVE-2023-1541
GitHub Security Advisory for CVE-2023-1541
GHSA-h2wg-83fc-xvm9 · Severity: low · Ecosystem: go
— Answer vulnerable to Business Logic Errors
Affected software / configurations for CVE-2023-1541
Vendor
Product
Version
Raw CPE
answer
answer
< 1.0.6
cpe:2.3:a:answer:answer:*:*:*:*:*:*:*:*
References for CVE-2023-1541
cvelogic
Threat Intelligence