dbcve.org
Ads By Datafeedr.comWordPress extension · Datafeedr

CVE-2023-49169

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-15
Fix available
A fix is available. Upgrade to after 1.2.0 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in datafeedr.Com Ads by datafeedr.Com allows Stored XSS.This issue affects Ads by datafeedr.Com: from n/a through 1.2.0.

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 · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in datafeedr.Com Ads plugin allows attackers to inject malicious scripts through unsanitized input that gets stored and rendered in web pages. The improper neutralization of input during page generation enables the execution of attacker-controlled JavaScript in victim browsers.

MitigationImplement proper input validation and output encoding/escaping on all user-supplied data before rendering in HTML context. Use established sanitization functions appropriate for the platform (e.g., esc_html(), esc_attr() in WordPress) and Content Security Policy headers to mitigate XSS risks.

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
Ads By Datafeedr.comWordPress extension
Affected:<= 1.2.0

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. Verify Datafeedr Ads plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Datafeedr Ads By Datafeedr.com' in the list
    Affected if plugin is present in the WordPress installation
  2. Check the installed version number
    In Plugins list, find the Datafeedr Ads plugin and note the version number displayed beneath the plugin name. Alternatively, check the plugin file header in /wp-content/plugins/datafeedr-ads/ or similar path
    Affected if version is 1.2.0 or lower
  3. Identify plugin configuration fields
    Navigate to the plugin settings page in WordPress admin (usually under Settings or a dedicated Datafeedr menu). Locate any input fields that accept user-supplied text such as ad configurations, API keys, or custom text fields
    Affected if plugin settings page with text input fields exists and is accessible
  4. Inspect stored data for unsanitized content
    Examine the plugin database tables (typically in wp_options or custom tables created by the plugin) for any stored values containing HTML script tags, javascript: URIs, or event handler attributes like onload/onerror
    Affected if database contains raw unsanitized user input that includes HTML tags or JavaScript code
  5. Review rendered page source for XSS payloads
    View the source code of pages where Datafeedr Ads content is displayed. Search for unescaped user input that appears as raw HTML or contains quote characters in attribute contexts
    Affected if rendered pages display user input without proper HTML encoding or attribute escaping

User is affected if the Datafeedr Ads plugin version is 1.2.0 or lower AND the plugin is actively storing or displaying user-supplied text in web pages without sanitization.

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.

From vendor data
Upgrade available Upgrade to a release after 1.2.0
Interim mitigation

Implement proper input validation and output encoding/escaping on all user-supplied data before rendering in HTML context. Use established sanitization functions appropriate for the platform (e.g., esc_html(), esc_attr() in WordPress) and Content Security Policy headers to mitigate XSS risks.

Fix this in Ads By Datafeedr.com 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-2023-49169 — 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-2023-49169 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