Approved changes feed: RSS · Atom
cpe:2.3:a:mailerup:mailerup:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Mailerup (4845bff0-f2f7-5d48-a7c5-0966604d7993) |
|---|---|
| Product | Mailerup (bc538c5b-9cbf-5e2a-bd4c-fb9766b49a25) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-13164 |
vulnerable | 2026-07-29 00:23:32.861047 |
Unauthenticated self-registration in MailerUp allows access to stored email data
Missing Authentication for Critical Function (CWE-306) in the RegisterView (apps/accounts/views.py), exposed at POST /api/auth/register/, in MailerUp <1.0.1 allows a remote, unauthenticated attacker to self-register a working account on instances where registration is intended to be restricted, because the endpoint applies the AllowAny permission with no email verification, CAPTCHA, or administrator approval. Any account created this way can read all email stored by the instance, resulting in full disclosure of stored messages to an arbitrary unauthenticated attacker
Published: 2026-06-24T15:37:17.398Z
Updated: 2026-06-24T16:43:56.757Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-13163 |
vulnerable | 2026-07-29 00:23:32.860724 |
Lack of input validation in Mailerup input parameter leads to Open Redirect
Open redirect vulnerability (CWE-601) in the _safe_redirect function of the click-tracking endpoint (/c/<token>/) in Mailerup <1.0.0 on all platforms allows remote unauthenticated attackers to redirect victims to arbitrary external sites and conduct phishing attacks via a crafted u query parameter, because the URL scheme is validated (blocking javascript: and data:) but the destination host is not restricted to an allowlist, and a signing.BadSignature exception is silently caught so a valid signed token is not required.
Published: 2026-06-24T12:49:05.227Z
Updated: 2026-06-24T13:07:07.003Z |
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.