LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1086: Font Pairing Preview For Landing Pages <= 1.3 - Cross-Site Request Forgery to Settings Update

The Font Pairing Preview For Landing Pages plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3. This is due to missing nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to modify the plugin's font pairing settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1086 affects the WordPress plugin Font Pairing Preview For Landing Pages through version 1.3. If an administrator is tricked into clicking a crafted link or taking a similar action, an attacker could change the plugin’s font pairing settings. The impact is limited to integrity of plugin settings, not data theft or server takeover based on available sources.

Executive priority

Treat as a routine but timely WordPress hygiene issue. Prioritize sites where administrators frequently manage content or where unwanted visual changes could affect brand trust. It does not currently warrant emergency response unless unexpected settings changes are observed.

Technical view

The issue is CWE-352 cross-site request forgery in the plugin’s settings update functionality, attributed to missing nonce validation. The CVSS 3.1 score is 4.3 with network attack vector, no privileges required, user interaction required, and low integrity impact. Public references point to the settings PHP file in trunk and tag 1.3.

Likely exposure

Exposure is limited to WordPress sites with Font Pairing Preview For Landing Pages installed at version 1.3 or earlier. Successful exploitation requires a logged-in administrator to perform an attacker-induced action. Sites not using this plugin are not affected by the described issue.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. Exploitation depends on social engineering an administrator and would modify plugin settings rather than directly execute code or access sensitive data, according to the provided CVSS and description.

Researcher notes

Evidence identifies missing nonce validation on settings update functionality. The public record names versions up to and including 1.3, but no fixed version or patch details are provided in the bundle. Avoid assuming remediation beyond vendor guidance or disabling/removing the plugin.

Mitigation direction

  • Inventory WordPress sites for Font Pairing Preview For Landing Pages version 1.3 or earlier.
  • Check the plugin vendor or WordPress plugin page for updated guidance or a fixed release.
  • Disable or remove the plugin where it is not business-critical.
  • Warn WordPress administrators not to click unsolicited links while authenticated.

Validation and detection

  • Confirm whether the plugin is installed and identify its version.
  • Review plugin settings for unexpected font pairing changes.
  • Check administrative activity around the time settings changed.
  • Verify vendor guidance before marking the issue remediated.
Prepared
Confidence
medium
Sources
5

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

CVE-2026-1086 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
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

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
4Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-1086Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
wpsolutionsFont Pairing Preview For Landing Pages0unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

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.