Plugins · wp-parsidate · data as of 2026-11-04
Is Parsi Date safe? Known vulnerabilities and latest version
- Latest version
- 6.5.2
- Last updated
- 2026-11-01
- Active installs
- 100,000+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Persian date support for WordPress and WooCommerce — by Morteza Geransayeh
What to do
- Update to the latest version (6.5.2). Anything older than 6.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get wp-parsidate --field=version shows what you run; wp plugin update wp-parsidate updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 7.1 CVE-2026-96836 · published 2026-09-30
Cross-site scripting (XSS) in Parsi Date (6.3 and older)
- Affected
- 6.3 and older
- Fixed in
- 6.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Cross Site Scripting (XSS) in Parsi Date <= 6.3 versions.
medium 6.1 CVE-2024-11032 · published 2024-11-26
Reflected cross-site scripting (XSS) in Parsi Date (5.1.1 and older)
- Affected
- 5.1.1 and older
- Fixed in
- 5.1.2 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Parsi Date plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 5.1.1. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
NVD CVE-2024-11032Wordfence advisoryCode change (fix)wordpress.orgPlugin source
Recent activity
- 2026-11-01 — latest release on wordpress.org (6.5.2).
- 2026-09-30 — Cross-site scripting (XSS) disclosed (CVE-2026-96836), fixed in 6.4.
- 2024-11-26 — Reflected cross-site scripting (XSS) disclosed (CVE-2024-11032), fixed in 5.1.2.
Get an email when Parsi Date has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Parsi Date (wp-parsidate) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (2)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-parsidate (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/wp-parsidate"><img src="https://laskyr.com/plugins/wp-parsidate/badge.svg" alt="Parsi Date vulnerability status"></a>