dbcve.org
Auto Amazon LinksWordPress extension · Michaeluno

CVE-2023-52175

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to 5.1.2 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 Michael Uno (miunosoft) Auto Amazon Links – Amazon Associates Affiliate Plugin allows Stored XSS.This issue affects Auto Amazon Links – Amazon Associates Affiliate Plugin: from n/a through 5.1.1.

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

A Stored XSS vulnerability exists in the Auto Amazon Links WordPress plugin (versions through 5.1.1) due to improper neutralization of user input during web page generation. Attackers can inject malicious scripts that persist in the database and execute when other users view affected pages.

MitigationUpdate to the latest version of the plugin once available, or deactivate the plugin until a patch is released. Implement proper input sanitization and output encoding using WordPress escaping functions (esc_html, esc_attr, wp_kses) on all user-supplied data before rendering.

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
Auto Amazon LinksWordPress extension
Affected:< 5.1.2

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 the plugin is installed
    Check your WordPress installation under wp-content/plugins/ for a folder named 'auto-amazon-links' or similar, or look for the plugin in the WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder or listing exists in your WordPress plugins directory.
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find Auto Amazon Links. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file header in the plugin folder for the 'Version' tag.
    Affected if The version displayed is lower than 5.1.2 (for example, 5.1.1, 5.1.0, or earlier).
  3. Inspect stored plugin settings in the database
    Access your WordPress database (via phpMyAdmin or command line) and examine the options table (typically wp_options) for rows where option_name contains 'auto.amazon.links' or similar plugin-related prefixes. Review the option_value field for any unsanitized HTML or script tags.
    Affected if You find HTML script tags, javascript: URIs, or event handler attributes (like onclick, onload) stored in plugin-related option values.
  4. Examine Amazon Links post meta data
    Query the postmeta table (typically wp_postmeta) for meta_key values related to the plugin (search for 'amazon_links' or similar). Review the meta_value for any injected script content.
    Affected if The meta_value fields contain script tags, iframe tags, or other potentially malicious HTML/JavaScript that was not intentionally added.
  5. Review pages displaying plugin output
    Visit pages on your site where Amazon Links shortcodes or widgets are used. View the page source and search for any unexpected script tags, foreign iframes, or suspicious inline JavaScript that matches known XSS patterns.
    Affected if Unexpected script tags or malicious code appears in the HTML output of pages using the plugin.

You are affected if the Auto Amazon Links plugin is installed with a version lower than 5.1.2 and either stored plugin settings or output pages contain unsanitized script injections.

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 5.1.2 or later
Fixed in 5.1.2
Interim mitigation

Update to the latest version of the plugin once available, or deactivate the plugin until a patch is released. Implement proper input sanitization and output encoding using WordPress escaping functions (esc_html, esc_attr, wp_kses) on all user-supplied data before rendering.

Recommended fix High confidence

5.1.2

  1. Back up your WordPress site before making any changes
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find 'Auto Amazon Links' in the plugin list
  5. Click 'Update now' if an update is available, or manually update to version 5.1.2
  6. Verify the plugin version is 5.1.2 or higher after updating

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

Fix this in Auto Amazon Links Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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