CVE-2025-1510: The The Custom Post Type Date Archives plugin for WordPress is vulnerable to arbitrary shortcode execution in

Q: How do I fix CVE-2025-1510?

custom post type date archives: upgrade to newer than 2.7.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-1510 being exploited?

CVE-2025-1510 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-1510 affect?

CVE-2025-1510 affects custom post type date archives. Severity is high (CVSS 7.3). The The Custom Post Type Date Archives plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.7.1. This is due to the software allowing users to execute an action that does not properly v

Q: How urgent is CVE-2025-1510?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.3REMOTEUPGRADE

CVE-2025-1510 is a high-severity flaw (CVSS 7.3) affecting custom post type date archives. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The The Custom Post Type Date Archives plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.7.1. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-94
Published	2025-02-22
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: keesiemeijer

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-22 04:15 UTCPublished CVE record published
2026-06-17 08:39 UTCUpdated Record last modified

keesiemeijer custom post type date archives UPGRADE

Affected: <= 2.7.1

Fixed in: newer than 2.7.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy custom-post-type-date-archives || rpm -q custom-post-type-date-archives || custom-post-type-date-archives --version

2. UPGRADE to newer than 2.7.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade custom-post-type-date-archives

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade custom-post-type-date-archives

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1510?

custom post type date archives: upgrade to newer than 2.7.1. Exact commands for each OS are on this page.

Is CVE-2025-1510 being exploited?

CVE-2025-1510 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1510 affect?

CVE-2025-1510 affects custom post type date archives. Severity is high (CVSS 7.3). The The Custom Post Type Date Archives plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.7.1. This is due to the software allowing users to execute an action that does not properly v

How urgent is CVE-2025-1510?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs