Security readout for executives and security teams
Plain-English summary
CVE-2026-1377 affects the WordPress imwptip plugin through version 1.1. An attacker could trick an administrator into clicking a crafted link or visiting a page, causing plugin settings to change without approval. The impact is limited to integrity of plugin configuration, but it matters for sites relying on those settings.
Executive priority
Treat this as a moderate website integrity issue. It is not currently reported as exploited, but WordPress administrators can be targeted through phishing-style interaction. Address during normal vulnerability remediation cycles, faster for high-value public sites or sites where plugin settings affect user trust or business workflows.
Technical view
The issue is cross-site request forgery in imwptip settings update handling. Sources attribute it to missing nonce validation, allowing unauthenticated attackers to submit forged settings-update requests if a logged-in site administrator performs a required action. CVSS is 4.3, reflecting network attackability, low complexity, required user interaction, and low integrity impact.
Likely exposure
Exposure is limited to WordPress sites with imwptip installed at version 1.1 or earlier. The provided data does not identify other affected products. Internet exposure depends on normal administrator access to the WordPress dashboard and whether an attacker can lure an administrator into an action.
Exploitation context
The source bundle does not indicate active exploitation, and KEV status is false. Exploitation requires user interaction by a site administrator. The vulnerability does not directly provide code execution or data theft based on the provided CVSS and description.
Researcher notes
The CVE record and Wordfence describe CSRF caused by missing nonce validation in settings updates. Public WordPress Trac links point to the plugin admin code for trunk and tag 1.1. The bundle does not name a fixed version, patch commit, or confirmed exploitation, so remediation guidance should remain vendor-driven.
Mitigation direction
- Inventory WordPress sites for the imwptip plugin and installed version.
- Prioritize sites running imwptip version 1.1 or earlier.
- Check WordPress plugin and vendor guidance for an updated or corrected release.
- Disable or remove the plugin where it is not business-critical.
- Remind administrators to avoid unexpected links while logged into WordPress.
Validation and detection
- Confirm whether imwptip is installed on each WordPress site.
- Record the installed plugin version and compare against version 1.1 or earlier.
- Review plugin settings for unauthorized or unexpected changes.
- Verify whether settings update handling includes nonce validation in the deployed code.
- Monitor vendor and Wordfence entries for remediation updates.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2026-1377 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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.
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:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/0fe987f0-6887-4ad1-a748-eb987bb574fa?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/imwptip/trunk/classes/imwptipadmin.php#L11CVE reference
- https://plugins.trac.wordpress.org/browser/imwptip/tags/1.1/classes/imwptipadmin.php#L11CVE reference
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.