dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-14734

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Amazon affiliate lite Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.0. This is due to missing or incorrect nonce validation on the 'ADAL_settings_page' function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Amazon affiliate lite WordPress plugin is vulnerable to Cross-Site Request Forgery (CSRF) due to missing nonce validation in the 'ADAL_settings_page' function. This allows unauthenticated attackers to forge administrative requests and modify plugin settings by tricking site administrators into clicking malicious links.

MitigationUpdate the plugin to version 1.0.1 or later which implements proper nonce validation, or manually add wp_nonce_field() verification to the ADAL_settings_page function.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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. Locate Amazon affiliate lite plugin
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Amazon Affiliate Lite' or check the plugin directory /wp-content/plugins/ for amazon-affiliate-lite folder
    Affected if Plugin is installed and active
  2. Identify installed version
    Check the plugin header comment in the main PHP file (usually amazon-affiliate-lite.php) for the Version: field, or view plugin details in WordPress admin plugins list
    Affected if Version is unknown, missing, or lower than 1.0.1
  3. Verify vulnerable function exists
    Search the plugin files for the function 'ADAL_settings_page' - check main plugin file or files in includes/ subfolder
    Affected if Function ADAL_settings_page exists in the codebase
  4. Check for nonce validation in settings function
    Examine the ADAL_settings_page function code for presence of wp_nonce_field() or wp_verify_nonce() or check_admin_referer() calls
    Affected if The function exists but contains no nonce verification logic

User is affected if Amazon affiliate lite plugin is installed with version lower than 1.0.1 and the ADAL_settings_page function lacks nonce validation checks.

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

Update the plugin to version 1.0.1 or later which implements proper nonce validation, or manually add wp_nonce_field() verification to the ADAL_settings_page function.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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