Home/CVE/A vulnerability was determined in Bagisto up to 2.3.15. Affected by this vulnerability is an unknown functionality of th
CVE
CVE-2026-6745
A vulnerability was determined in Bagisto up to 2.3.15. Affected by this vulnerability is an unknown functionality of th
A vulnerability was determined in Bagisto up to 2.3.15. Affected by this vulnerability is an unknown functionality of the component Custom Scripts Handler. This manipulation causes cross site scripting.
Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure and explains: "We already replied on the github advisories.
All the security issues are addressed through security advisory. We will fix this in our upcomming releases.".
LOW · CVSS 3.5
EPSS 0.00034
EPSS exploitation odds0.03% · top 89%
Monitor
- No active-exploitation, high-EPSS, or public-exploit signals - routine patching cadence
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-6745, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
0.03%
Top 89%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
no
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:NLifecycle
- 21 Apr 2026Published to NVD
- 29 Apr 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWE → CAPEC → ATT&CK. Pills with a solid outline are named directly in ATT&CK or Nuclei templates (high confidence); the others are linked through weakness mappings.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
9Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-209 · XSS Using MIME Type Mismatch CAPEC-CAPEC-242 · Code Injection CAPEC-CAPEC-35 · Leverage Executable Code in Non-Executable Files CAPEC-CAPEC-588 · DOM-Based XSS CAPEC-CAPEC-591 · Reflected XSS CAPEC-CAPEC-592 · Stored XSS CAPEC-CAPEC-63 · Cross-Site Scripting (XSS) CAPEC-CAPEC-77 · Manipulating User-Controlled Variables CAPEC-CAPEC-85 · AJAX Footprinting
⬡
Weakness Classification
▤
Affected Packages
1Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Packagist
bagisto/bagisto
LOW
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2000-1205
Cross site scripting vulnerabilities in Apache 1.3.0 through 1.3.11 allow remote...
same CWE-79
CVE-2002-0270
Opera, when configured with the "Determine action by MIME type" option disabled,...
same CWE-79
CVE-2002-1651
Cross-site scripting (XSS) vulnerability in Verity Search97 allows remote attack...
same CWE-79
CVE-2002-1700
Cross-site scripting vulnerability (XSS) in the missing template handler in Macr...
same CWE-79
CVE-1999-0509
Perl, sh, csh, or other shell interpreters are installed in the cgi-bin director...
same CWE-94
CVE-1999-0491
The prompt parsing in bash allows a local user to execute commands as another us...
same CWE-94
CVE-1999-0891
The "download behavior" in Internet Explorer 5 allows remote attackers to read a...
same CWE-94
CVE-1999-0702
Internet Explorer 5.0 and 5.01 allows remote attackers to modify or execute file...
same CWE-94
🔗
References & Sources
4Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.