LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25144: WP HTML Mail < 2.2.11 - HTML injection

The WP HTML Mail plugin for WordPress is vulnerable to HTML injection in versions up to, and including, 2.2.10 due to insufficient input sanitization. This makes it possible for unauthenticated attackers to inject arbitrary HTML in pages that execute if they can successfully trick a administrator into performing an action such as clicking on a link.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects WordPress sites using the WP HTML Mail plugin through version 2.2.10. An unauthenticated attacker could inject HTML if they trick an administrator into taking an action such as clicking a link. Impact is limited to confidentiality and integrity, with no availability impact described.

Executive priority

Treat as a moderate-priority WordPress plugin issue. Prioritize internet-facing or business-critical sites, especially where multiple administrators can be targeted. It is not KEV-listed in the provided data, but cleanup is still warranted because exploitation only needs administrator interaction.

Technical view

The issue is insufficient input sanitization leading to HTML injection, mapped to CWE-79. CVSS 3.1 is 5.4: network-reachable, low complexity, no privileges required, user interaction required, unchanged scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is likely limited to WordPress installations running WP HTML Mail versions up to and including 2.2.10. The bundled affected-product metadata is inconsistent, so asset validation should focus on installed plugin name and version.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The attack scenario requires social engineering an administrator into performing an action, which lowers urgency but does not remove risk.

Researcher notes

The CVE description names WP HTML Mail through 2.2.10, while the affected metadata lists a different product as unaffected. Use the narrative description, title, and external references to guide investigation, and preserve this inconsistency in tracking notes.

Mitigation direction

  • Upgrade WP HTML Mail beyond version 2.2.10 where available.
  • Check vendor and Wordfence guidance for exact fixed versions.
  • Remove or disable the plugin if it is unused.
  • Warn administrators about unexpected plugin-related links or prompts.
  • Review WordPress admin accounts for unnecessary privileges.

Validation and detection

  • Inventory WordPress sites for the WP HTML Mail plugin.
  • Confirm installed plugin versions are not 2.2.10 or older.
  • Check web logs for suspicious administrator-targeted requests.
  • Review recent administrator activity for unexpected content changes.
  • Confirm remediation in staging before production rollout.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-79: 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 lookup
cve · low confidence lookup

CVE-2019-25144 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2019-25144Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
a3revWP Email Template0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.