dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-10487

HIGH · 7.3 CVSS v3.1 Published 2025-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Advanced Ads – Ad Manager & AdSense plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.0.12 via the select_one() function. This is due to the endpoint not properly restricting access to the AJAX endpoint or limiting the functions that can be called to safe functions. This makes it possible for unauthenticated attackers to call arbitrary functions beginning with get_the_ like get_the_excerpt which can make information exposure possible.

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 Advanced Ads WordPress plugin has an unauthenticated AJAX endpoint vulnerability in the select_one() function that allows attackers to call arbitrary functions starting with get_the_ (like get_the_excerpt). This occurs because the endpoint lacks proper access restrictions and doesn't whitelist safe functions, enabling information disclosure and potential remote code execution.

MitigationUpgrade to version 2.0.13 or later immediately. Until then, consider disabling the plugin or blocking AJAX endpoint access at the web server level.

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

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
Low
Integrity
Low
Availability
Low

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

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 Advanced Ads plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate Advanced Ads. Check the version number displayed under the plugin name.
    Affected if The plugin is installed and active on the site.
  2. Compare installed version to affected range
    Note the installed version number. Versions before 2.0.13 are vulnerable. Versions 2.0.13 and later contain the fix.
    Affected if The installed version is lower than 2.0.13.
  3. Identify the vulnerable AJAX endpoint
    Check if the file /wp-admin/admin-ajax.php responds to the 'select_one' action. This can be tested by sending a POST request to your site with action=select_one and a parameter that triggers get_the_excerpt or similar functions.
    Affected if The endpoint responds without authentication (user not logged in) and accepts arbitrary function names starting with get_the_.
  4. Inspect the select_one function code
    If you have file access, locate the Advanced Ads plugin files (typically in /wp-content/plugins/advanced-ads/) and examine the select_one() function. Look for missing capability checks or nonce verification, and verify whether function calls are restricted to a whitelist.
    Affected if The function lacks access control, does not verify nonces, or allows calling any function matching the get_the_* pattern.

You are affected if Advanced Ads plugin is installed with a version lower than 2.0.13 AND the admin-ajax.php endpoint is accessible without authentication and accepts arbitrary get_the_* function calls.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.0.13 or later immediately. Until then, consider disabling the plugin or blocking AJAX endpoint access at the web server level.

Recommended fix Moderate confidence

Advanced Ads – Ad Manager & AdSense version 2.0.13

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Advanced Ads – Ad Manager & AdSense' in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest patched version
  5. Alternatively, use WP-CLI: wp plugin update advanced-ads
  6. After updating, verify the version is 2.0.13 or later in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10487 — 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-10487 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