dbcve.org
Wp AdcenterWordPress extension · Wpeka

CVE-2024-10113

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to after 2.5.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 WP AdCenter – Ad Manager & Adsense Ads plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpadcenter_ad shortcode in all versions up to, and including, 2.5.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 WP AdCenter plugin for WordPress contains a stored XSS vulnerability in versions up to 2.5.7. The vulnerability exists in the wpadcenter_ad shortcode handler, which fails to properly sanitize and escape user-supplied attributes before outputting them in HTML. An attacker with contributor-level access can embed malicious JavaScript in shortcode attributes that will execute when other users view affected pages.

MitigationUpdate the WP AdCenter plugin to version 2.5.8 or later, which includes proper input sanitization and output escaping for shortcode attributes. If unable to update immediately, restrict contributor-level user permissions or disable the wpadcenter_ad shortcode until the patch can be applied.

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
Wp AdcenterWordPress extension
Affected:<= 2.5.7

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Check if WP AdCenter plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wpeka Wp Adcenter' or check the plugin files in wp-content/plugins/
    Affected if The plugin is not installed or not present in the system
  2. Identify the installed version of WP AdCenter
    In WordPress admin, go to Plugins > Installed Plugins, find WP AdCenter, and note the version number displayed below the plugin name
    Affected if Version is 2.5.7 or lower (any version up to and including 2.5.7)
  3. Search for wpadcenter_ad shortcode usage in content
    Query the WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[wpadcenter_ad%' AND post_status IN ('publish','draft','pending','future')
    Affected if The shortcode is present in any published or draft content
  4. Inspect shortcode attributes for unsanitized input
    Examine any posts containing [wpadcenter_ad] shortcode; look at the attributes (such as ad_id, zone_id, or custom attributes) to see if they contain raw user input that might include HTML or JavaScript
    Affected if Shortcode attributes contain unescaped special characters like < > " or contain patterns resembling script tags or event handlers

You are affected if the WP AdCenter plugin version is 2.5.7 or lower AND the wpadcenter_ad shortcode is being used on your site with user-supplied attributes that are not properly escaped.

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.5.7
Interim mitigation

Update the WP AdCenter plugin to version 2.5.8 or later, which includes proper input sanitization and output escaping for shortcode attributes. If unable to update immediately, restrict contributor-level user permissions or disable the wpadcenter_ad shortcode until the patch can be applied.

Recommended fix Moderate confidence

Upgrade to WP AdCenter version 2.5.8 or later (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP AdCenter – Ad Manager & Adsense Ads in the plugin list
  4. Check the current installed version to confirm it is 2.5.7 or below
  5. If an update is available, click 'Update Now' to update the plugin to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/wp-admanager and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number in the Plugins list
  8. Test that the wpadcenter_ad shortcode functions correctly on your site

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

Fix this in Wp Adcenter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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