CVE-2026-39482

Post Expirator <= 4.9.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

2026-03-22 00:00
timomangcut

Strategic Overview

Status
Patched in 4.10.0
Affected Plugin
Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories
Affected Version
<= 4.9.4
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2026-39482
View all Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories vulnerabilities

At a glance

CVE-2026-39482 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Schedule Post Changes With PublishPress Future WordPress plugin, affecting versions <= 4.9.4. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.10.0; sites on affected versions should update now. Disclosed March 2026, reported by timomangcut.

Vulnerability Overview

The Post Expirator plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 4.9.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

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

Reaching this weakness in Schedule Post Changes With PublishPress Future <= 4.9.4 takes an account at Contributor level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Schedule Post Changes With PublishPress Future the fix is 4.10.0: builds <= 4.9.4 are affected, anything from 4.10.0 onward is not.

Remediation

Update to version 4.10.0, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Schedule Post Changes With PublishPress Future 4.10.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-39482https://www.wordfence.com/threat-intel/vulnerabilities/id/51ca3ed9-6c3e-44c6-b746-8415e27abed0https://nvd.nist.gov/vuln/detail/CVE-2026-39482

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C