LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1088: Login Page Editor <= 1.2 - Cross-Site Request Forgery to Settings Update

The Login Page Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing nonce validation on the devotion_loginform_process() AJAX action. This makes it possible for unauthenticated attackers to update the plugin's login page 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-1088 affects the WordPress Login Page Editor plugin through version 1.2. A malicious site or link could cause a logged-in administrator’s browser to change plugin login page settings. This requires tricking an administrator, so business impact is limited but relevant for WordPress sites using this plugin.

Executive priority

Treat this as a routine but time-bound WordPress hygiene issue. Prioritize sites where administrators frequently manage content from browsers exposed to email or web links. It is not currently supported as an emergency active-exploitation case by the provided sources.

Technical view

The issue is CWE-352 cross-site request forgery in the devotion_loginform_process() AJAX action due to missing nonce validation. It is network reachable, requires no attacker privileges, and requires user interaction from an administrator. CVSS is 4.3, with low integrity impact and no stated confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress installations running Login Page Editor up to and including version 1.2. Organizations not using this plugin are not affected. The provided affected-version metadata is inconsistent, so validate against the narrative description and vendor intelligence.

Exploitation context

The sources describe a forged request that can update login page settings if an administrator is tricked into taking an action. The CVE is not listed as KEV, and the provided sources do not state active exploitation or public weaponization.

Researcher notes

The key evidence is missing nonce validation on the AJAX settings update path. Source references include Wordfence and WordPress plugin Trac locations. The CVE record’s structured affected data appears inconsistent with the prose claim of all versions up to 1.2, so confirm against live vendor data.

Mitigation direction

  • Identify WordPress sites using Login Page Editor version 1.2 or earlier.
  • Check the plugin vendor or WordPress plugin page for updated guidance.
  • Update if a fixed version is available from the vendor.
  • Disable or remove the plugin where it is not required.
  • Warn administrators against interacting with untrusted links while logged in.

Validation and detection

  • Inventory installed WordPress plugins and versions across managed sites.
  • Confirm whether Login Page Editor is present and at version 1.2 or earlier.
  • Review plugin settings for unexpected login page changes.
  • Check security monitoring for suspicious administrator-initiated settings updates.
  • Track Wordfence and CVE records for remediation updates.
Prepared
Confidence
high
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-1088 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-1088Attack 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
zero1zeroukLogin Page Editor0unaffected
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.