CVE-2026-1877
Received Received - Intake
CSRF Vulnerability in Auto Post Scheduler Plugin Allows Settings Manipulation

Publication date: 2026-03-31

Last updated on: 2026-03-31

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-31
Last Modified
2026-03-31
Generated
2026-05-27
AI Q&A
2026-03-31
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wp-plugins auto_post_scheduler to 1.84 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Auto Post Scheduler plugin for WordPress, up to and including version 1.84, is vulnerable to a Cross-Site Request Forgery (CSRF) attack. This vulnerability arises because the plugin's 'aps_options_page' function lacks nonce validation, which is a security measure to verify the authenticity of requests. As a result, an attacker can trick a site administrator into performing unintended actions, such as clicking on a malicious link, which then allows the attacker to update plugin settings or inject malicious web scripts without authentication.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in the Auto Post Scheduler plugin allows unauthenticated attackers to perform Cross-Site Request Forgery (CSRF) attacks, potentially enabling them to update settings and inject malicious scripts by tricking an administrator. This could lead to unauthorized changes in website behavior and possible exposure of sensitive data.

Such unauthorized access and potential data manipulation could negatively impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal data and secure system configurations to prevent unauthorized access or data breaches.

However, the provided information does not explicitly detail the direct impact on compliance frameworks or specific regulatory requirements.


How can this vulnerability impact me? :

This vulnerability can allow an unauthenticated attacker to modify the settings of the Auto Post Scheduler plugin by exploiting the administrator's session through a forged request. This can lead to the injection of malicious scripts into the website, potentially compromising the site's integrity and security. The attacker could manipulate scheduled posts or other plugin configurations, which might result in unauthorized content being published or harmful code being executed on the site.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves Cross-Site Request Forgery (CSRF) due to missing nonce validation in the 'aps_options_page' function of the Auto Post Scheduler WordPress plugin up to version 1.84.

Detection can focus on monitoring for unauthorized changes to the plugin's settings or suspicious POST requests targeting the plugin's options page.

  • Check WordPress logs or the plugin's custom database table 'aps_log' for unusual entries or errors related to scheduling or options updates.
  • Use web server access logs to identify unexpected POST requests to the admin options page URL of the Auto Post Scheduler plugin.
  • Commands to assist detection might include:
  • 1. Using grep to find POST requests to the plugin options page in web server logs, e.g., `grep 'POST.*aps_options_page' /var/log/apache2/access.log`
  • 2. Querying the WordPress database for recent changes in the 'aps_log' table: `SELECT * FROM aps_log ORDER BY date DESC LIMIT 10;`
  • 3. Monitoring WordPress admin activity logs (if available) for changes to Auto Post Scheduler settings.

What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, immediate steps include:

  • Update the Auto Post Scheduler plugin to a version later than 1.84 where the nonce validation issue is fixed.
  • Restrict access to the WordPress admin area to trusted users only, minimizing the risk of an attacker tricking an administrator.
  • Implement additional security measures such as Web Application Firewalls (WAF) to detect and block forged requests.
  • Educate site administrators to avoid clicking on suspicious links that could trigger CSRF attacks.
  • Consider temporarily disabling the Auto Post Scheduler plugin if an immediate update is not available.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart