Authenticated stored XSS via unsanitized Schedule Name
Published Jun 1, 2021 · Updated Aug 3, 2024
Cross-site scripting in Weekly Schedule before 3.4.3 allows remote authenticated users to execute JavaScript via the Schedule Name setting. The general-options Schedule Name value is stored without proper sanitization, allowing script tags to persist and execute when the value is rendered. Exploitation requires an authenticated account that can edit plugin general options and a victim browser viewing the stored value, resulting in script execution in that WordPress context.
Summary
What happened
Cross-site scripting in Weekly Schedule before 3.4.3 allows remote authenticated users to execute JavaScript via the Schedule Name setting. The general-options Schedule Name value is stored without proper sanitization, allowing script tags to persist and execute when the value is rendered. Exploitation requires an authenticated account that can edit plugin general options and a victim browser viewing the stored value, resulting in script execution in that WordPress context.
The record
- CVE
- CVE-2021-24309
- Published
- Jun 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Yannick Lefebvre
- Product
- Weekly Schedule
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.4.3 <3.4.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Weekly Schedule Schedule Name stored XSS proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo