Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker may email a malicious attachment to a configured CRM mailbox and cause the WordPress plugin to store it outside its protected attachment directory. If the server executes PHP in uploads, the attacker could take control of the site, access sensitive business data, alter records, or disrupt service.
Executive priority
Treat exposed configurations as an immediate remediation priority because compromise could become full site takeover without an authenticated account. Identify affected sites today, disable the feature where practical, and confirm the vendor-supported fixed release before upgrading. Preserve relevant logs and investigate suspicious files if the vulnerable configuration was internet-reachable.
Technical view
Versions through 1.17.8 lack file-extension validation and path normalization in save_attachments() during CRM Email Connect IMAP processing. A crafted References header and traversal-style attachment filename can redirect an uploaded PHP file into wp-content/uploads. The cron-driven workflow requires no WordPress account. Remote code execution depends on PHP execution being permitted in uploads.
Likely exposure
Exposure requires the affected plugin at version 1.17.8 or earlier, with the CRM module and IMAP Email Connect enabled and configured. Sites are at greatest risk when PHP can execute from wp-content/uploads. Sites without the feature configuration are not shown by the supplied evidence to be exploitable through this path.
Exploitation context
The CVSS 3.1 score is 9.8 because the vulnerable workflow is network-accessible, requires no account or user interaction, and may compromise confidentiality, integrity, and availability. The supplied record is not in KEV, and the sources provide no evidence of active exploitation. Exploitation therefore remains possible but unconfirmed in the wild.
Researcher notes
The vulnerable boundary combines attacker-controlled email metadata, attachment filenames, filesystem path construction, and delayed cron execution. The WordPress changeset is relevant remediation evidence, but the supplied bundle does not explicitly name a fixed release. Defensive review should focus on normalization, extension enforcement, destination confinement, and whether server configuration converts an arbitrary upload into code execution.
Mitigation direction
- Check vendor guidance and move beyond version 1.17.8 once the fixed release is confirmed.
- Disable CRM Email Connect or inbound IMAP processing until remediation is verified.
- Configure the web server to prevent PHP execution within upload directories.
- Restrict and monitor access to the configured inbound mailbox.
Validation and detection
- Inventory WordPress sites for the plugin and record installed versions.
- Confirm whether CRM and IMAP Email Connect are enabled and configured.
- Determine whether PHP files can execute from wp-content/uploads.
- Review uploads for unexpected PHP files or suspicious recent attachments.
- Review IMAP synchronization and web logs for anomalous attachment processing.
- After remediation, confirm traversal filenames and disallowed extensions are rejected safely.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-18080 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b9d11eb9-5e18-459f-a9d4-cccb1d593402?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3656848/erpCVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.