Approved changes feed: RSS · Atom
cpe:2.3:a:jexactyl:jexactyl:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Jexactyl (6f397ddc-573f-5202-8a11-b5fef73c9484) |
|---|---|
| Product | Jexactyl (c410a5ff-0ed9-56b1-a76c-2cb1f58991f1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/jexactyl/jexactyl |
purl2cpe | 2026-06-01 10:16:57.277385 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-107852 |
vulnerable | 2026-11-03 10:15:59.080881 |
Jexactyl: Stripe checkout confirmation accepts mismatched-currency/amount payments as full payment (payment forgery)
Jexactyl is a customisable game management panel and billing system. Prior to 4.0.5, the POST /api/client/billing/stripe/process endpoint accepts a client-supplied Stripe Checkout Session when payment_status is paid but does not compare amount_total or currency with the referenced order and configured billing currency. On an instance where the billing module is enabled and a Stripe secret key is configured, an authenticated client can therefore complete a lower-value or mismatched-currency payment and cause the order to be processed, provisioning, renewing, upgrading, or unsuspending the purchased server for less than the required price. This issue is fixed in version 4.0.5.
Published: 2026-10-09T20:28:06.513Z
Updated: 2026-10-14T02:11:26.450Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33061 |
vulnerable | 2026-06-08 07:57:18.527848 |
Jexactyl has Stored DOM Cross-Site Scripting (XSS) via unescaped JSON in Blade template
MEDIUM (5.8)
Jexactyl is a customisable game management panel and billing system. Commits after 025e8dbb0daaa04054276bda814d922cf4af58da and before e28edb204e80efab628d1241198ea4f079779cfd inject server-side objects into client-side JavaScript through resources/views/templates/wrapper.blade.php. Using unescaped {!! json_encode(...) !!} without safe encoding flags allows string values to break out of the JavaScript context and be interpreted as HTML/JS by the browser. If any serialized fields contain attacker-controlled content, such as a username, display name, or site config value, a malicious payload will execute arbitrary script for any user viewing the page (stored DOM XSS). This issue has been patched by commit e28edb204e80efab628d1241198ea4f079779cfd.
Published: 2026-03-20T07:34:14.077Z
Updated: 2026-03-30T12:39:35.052Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.