LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1877: Auto Post Scheduler <= 1.84 - Cross-Site Request Forgery to Stored Cross-Site Scripting via aps_options_page

The Auto Post Scheduler plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.84. This is due to missing nonce validation on the 'aps_options_page' function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A vulnerable WordPress plugin can let an attacker abuse an administrator’s browser to change plugin settings and store malicious script on the site. The attacker must convince an admin to take an action, such as clicking a link. This is not listed as known exploited in KEV.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It can affect website integrity and visitor trust, but exploitation requires administrator interaction. Prioritize sites with public visibility, many administrators, or high brand impact.

Technical view

Auto Post Scheduler for WordPress, versions up to and including 1.84, lacks nonce validation in aps_options_page. This enables unauthenticated CSRF that can update settings and inject stored cross-site scripting when an authenticated administrator is tricked into submitting a forged request.

Likely exposure

Exposure is limited to WordPress sites with Auto Post Scheduler installed at version 1.84 or earlier. Risk depends on administrator interaction and whether vulnerable settings are reachable in the deployed configuration.

Exploitation context

The CVSS score is 6.1. Exploitation requires no attacker account but does require administrator user interaction. Public sources provided do not state active exploitation or a confirmed weaponized exploit.

Researcher notes

The reported root cause is missing nonce validation in aps_options_page, producing CSRF that can lead to stored XSS. CWE is listed as CWE-79. The provided sources do not identify a fixed version, so remediation should follow vendor guidance.

Mitigation direction

  • Inventory WordPress sites for Auto Post Scheduler version 1.84 or earlier.
  • Check the plugin vendor and Wordfence pages for updated remediation guidance.
  • Disable or remove the plugin if it is not business-critical.
  • Warn administrators against clicking unsolicited links while logged into WordPress.

Validation and detection

  • Confirm whether Auto Post Scheduler is installed on each WordPress site.
  • Record installed plugin versions and compare against affected versions through 1.84.
  • Review plugin settings for unexpected changes or injected script content.
  • Check web and WordPress logs for suspicious administrator setting 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-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-2026-1877 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
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
johnh10Auto Post Scheduler0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.