Wp Mail Logging
Approved changes feed: RSS · Atom
cpe:2.3:a:smub:wp_mail_logging:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Smub (de95b648-5e6e-5830-888e-6dff235e28e3) |
|---|---|
| Product | Wp Mail Logging (7975fc94-6ef1-5667-9f70-84f4ac671673) |
| 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-109401 |
vulnerable | 2026-11-03 10:17:39.353683 |
WP Mail Logging <= 1.17.0 - Authenticated (Administrator+) Sensitive Information Exposure in LIKE Wildcard in Personal Data Export Email
LOW (2.7)
The WP Mail Logging plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.17.0 via the 'email_address' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to extract complete logged mail rows belonging to other users — including recipient addresses, message subjects, full message bodies, and any URLs contained therein — whose addresses happen to match the wildcard. Exploitation requires an administrator to process a personal-data export request for the attacker's email address via the standard WordPress privacy workflow, and the attacker's address must contain a LIKE wildcard character (such as an underscore) that matches at least one other user's address in the mail log.
Published: 2026-10-16T06:41:07.717Z
Updated: 2026-10-16T14:21:19.789Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2471 |
vulnerable | 2026-06-08 07:55:17.095038 |
WP Mail Logging <= 1.15.0 - Unauthenticated PHP Object Injection via Email Log Message Field
HIGH (7.5)
The WP Mail Logging plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.15.0 via deserialization of untrusted input from the email log message field. This is due to the `BaseModel` class constructor calling `maybe_unserialize()` on all properties retrieved from the database without validation. This makes it possible for unauthenticated attackers to inject a PHP Object by submitting a double-serialized payload through any public-facing form that sends email (e.g., Contact Form 7). When the email is logged and subsequently viewed by an administrator, the malicious payload is deserialized into an arbitrary PHP object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.
Published: 2026-02-28T06:27:42.492Z
Updated: 2026-04-08T16:36:08.455Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-3081 |
vulnerable | 2026-06-08 06:09:38.451216 |
WP Mail Logging <= 1.11.1 - Unauthenticated Stored Cross-Site Scripting via Email
HIGH (7.2)
The WP Mail Logging plugin for WordPress is vulnerable to Stored Cross-Site Scripting via email contents in versions up to, and including, 1.11.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Note: An incomplete fix was released in 1.11.1.
Published: 2023-07-12T04:38:51.671Z
Updated: 2026-04-08T17:31:53.794Z |
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.