dbcve.org
Custom Post Type Date ArchivesApplication · Keesiemeijer

CVE-2025-1510

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-22
Fix available
A fix is available. Upgrade to after 2.7.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Custom Post Type Date Archives WordPress plugin up to version 2.7.1 is vulnerable to arbitrary shortcode execution due to improper validation of user input before passing it to the do_shortcode() function. Unauthenticated attackers can exploit this to execute any registered WordPress shortcode, potentially leading to data theft, site defacement, or privilege escalation.

MitigationUpdate the plugin to version 2.7.2 or later. If an update is unavailable, consider removing the plugin or implementing WAF rules to block requests to the vulnerable endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Custom Post Type Date ArchivesApplication
Affected:<= 2.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    Locate the plugin directory in wp-content/plugins/ and confirm the 'custom-post-type-date-archives' folder exists. Alternatively, check via WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder 'custom-post-type-date-archives' is present in the plugins directory
  2. Check installed plugin version
    Open the main plugin file (custom-post-type-date-archives.php) and look for the version number in the plugin header comment, typically found near the top of the file. You can also check in WordPress admin under Plugins > Installed Plugins where the version number is displayed.
    Affected if The reported version is 2.7.1 or lower
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if 'Custom Post Type Date Archives' shows as active. You can also query the wp_options table for the option_name 'active_plugins' and check if the plugin path is included.
    Affected if The plugin is currently activated on the site
  4. Assess exposure to unauthenticated users
    The vulnerability is exploitable by unauthenticated (logged-out) users. Verify that the plugin is accessible to visitors of the site. If the site allows public access and the plugin handles date archive queries, the vulnerable endpoint is reachable.
    Affected if The site accepts requests from unauthenticated users and the plugin handles URL parameters for date archives

If the Custom Post Type Date Archives plugin is installed, active, and running version 2.7.1 or lower, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.7.1
Interim mitigation

Update the plugin to version 2.7.2 or later. If an update is unavailable, consider removing the plugin or implementing WAF rules to block requests to the vulnerable endpoint.

Recommended fix High confidence

2.7.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "Custom Post Type Date Archives" in the plugin list
  4. Check if an update is available for the plugin
  5. If an update is available, click "Update Now" to install the latest version
  6. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  7. Verify the plugin has been updated to version 2.7.2 or higher after completion

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Custom Post Type Date Archives Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1510 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data