LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1087: The Guardian News Feed <= 1.2 - Cross-Site Request Forgery to Settings Update

The Guardian News Feed 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 settings update functionality. This makes it possible for unauthenticated attackers to modify the plugin's settings, including the Guardian API key, 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-1087 affects The Guardian News Feed WordPress plugin through version 1.2. A malicious site or link could cause a logged-in administrator to unknowingly change plugin settings, including the Guardian API key. The business impact is limited but real: configuration integrity can be compromised if administrators are tricked.

Executive priority

Handle in normal vulnerability management cadence, faster for public-facing or business-critical WordPress sites. The issue is not reported as actively exploited, but it can let attackers tamper with plugin configuration through administrator deception.

Technical view

The plugin’s settings update functionality lacks nonce validation, creating a CSRF issue classified as CWE-352. The CVSS v3.1 score is 4.3. Sources state unauthenticated attackers can submit forged requests if they induce a site administrator to perform an action, such as clicking a link.

Likely exposure

Exposure is limited to WordPress sites using The Guardian News Feed plugin versions up to and including 1.2. The attack requires administrator interaction, so broad automated compromise is less likely than with unauthenticated direct exploitation.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. Exploitation depends on social engineering a logged-in administrator into triggering a forged request. Do not treat this as actively exploited unless new vendor, KEV, or threat-intelligence evidence appears.

Researcher notes

Evidence identifies missing nonce validation in the settings update path. Public references include Wordfence and WordPress plugin source locations. The provided sources do not name a patched version, exploit-in-the-wild activity, or a vendor remediation notice.

Mitigation direction

  • Inventory WordPress sites for The Guardian News Feed plugin and version.
  • Check vendor or WordPress plugin guidance for a fixed release or official mitigation.
  • If no fix is available, consider disabling the plugin if not business-critical.
  • Educate administrators to avoid unsolicited links while logged into WordPress.

Validation and detection

  • Confirm whether the plugin is installed and at version 1.2 or earlier.
  • Review plugin settings for unexpected changes, especially the Guardian API key.
  • Check available vendor or WordPress plugin repository updates.
  • Verify settings update handling includes CSRF protection before considering risk resolved.
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-1087 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-1087Attack 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
openplatformThe Guardian News Feed0unaffected
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.