Security readout for executives and security teams
Plain-English summary
This vulnerability affects the WP Travel WordPress plugin through version 4.4.6. If an administrator is tricked into taking an action while logged in, an unauthenticated attacker could change metadata on travel posts. The business impact is limited data integrity risk, not system takeover based on the provided sources.
Executive priority
Treat as a routine patching item unless the organization relies heavily on WP Travel content integrity. Prioritize affected public WordPress sites, but this is not supported as an emergency issue by the provided evidence.
Technical view
CVE-2021-4389 is a CSRF issue in WP Travel caused by missing or incorrect nonce validation in save_meta_data(). The CVSS 3.1 score is 4.3 with required user interaction and low integrity impact. Sources identify versions up to and including 4.4.6 as affected.
Likely exposure
Exposure is limited to WordPress sites running WP Travel versions 4.4.6 or earlier. Sites without the plugin, or on a non-affected release, are not indicated as exposed by the provided sources.
Exploitation context
The provided sources do not indicate active exploitation, and the CVE is not marked KEV. Exploitation requires tricking a logged-in site administrator into performing an action such as clicking a link.
Researcher notes
Focus validation on nonce enforcement around save_meta_data() and the 4.4.7 changeset. Do not assume broader privilege escalation or confidentiality impact from the supplied sources; the described impact is metadata modification through CSRF with administrator interaction.
Mitigation direction
- Inventory WordPress sites for the WP Travel plugin and installed version.
- Update WP Travel to a non-affected release; 4.4.7 is referenced in the fix changeset.
- Review vendor and plugin guidance for current supported versions.
- Remind administrators to avoid unexpected links while logged into WordPress.
Validation and detection
- Confirm whether WP Travel is installed on each WordPress site.
- Verify the installed plugin version is newer than 4.4.6.
- Review travel post metadata for unexpected changes if exposure existed.
- Check vulnerability scanner results against CVE-2021-4389.
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-2021-4389 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/28dea1e9-e772-488e-b98f-93a46ab84581?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/changeset/2477827/wp-travel/tags/4.4.7/inc/admin/class-admin-metaboxes.phpCVE 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.