dbcve.org
AweberWordPress extension

CVE-2023-47757

HIGH · 8.8 CVSS v3.1 Published 2023-11-17
Fix available
A fix is available. Upgrade to 7.3.10 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Missing Authorization, Cross-Site Request Forgery (CSRF) vulnerability in AWeber AWeber – Free Sign Up Form and Landing Page Builder Plugin for Lead Generation and Email Newsletter Growth allows Accessing Functionality Not Properly Constrained by ACLs, Cross-Site Request Forgery.This issue affects AWeber – Free Sign Up Form and Landing Page Builder Plugin for Lead Generation and Email Newsletter Growth: from n/a through 7.3.9.

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

This is a combined CSRF and Missing Authorization vulnerability in the AWeber WordPress plugin. The plugin fails to validate CSRF tokens on sensitive admin actions AND doesn't properly check user permissions (authorization) before allowing access to privileged functionality. An attacker could trick an authenticated administrator into unknowingly executing actions like modifying plugin settings, changing sign-up form configurations, or accessing administrative functions they shouldn't have access to.

MitigationAdd anti-CSRF tokens (nonces) to all forms and AJAX endpoints, and implement proper capability checks (current_user_can()) before executing privileged operations. Ensure all state-changing requests require valid authentication and authorization.

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
AweberWordPress extension
Affected:< 7.3.10

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

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

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. Confirm AWeber plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Aweber' or 'AWeber' in the plugin list
    Affected if The plugin appears in the installed plugins list
  2. Check installed AWeber plugin version
    In Plugins list, click on the plugin name or look at the version column next to the AWeber plugin entry. Alternatively, open the main plugin file (likely aweber/aweber.php) and locate the 'Version' header in the plugin comments
    Affected if The version number displayed is less than 7.3.10 (for example, 7.3.9, 7.3.8, etc.)
  3. Verify plugin is active
    In WordPress admin > Plugins, check if the AWeber plugin shows as 'Active' rather than 'Inactive' or 'Network Active'
    Affected if The plugin is activated and in use on the site

You are affected if the AWeber WordPress plugin is installed, activated, and running version 7.3.9 or lower.

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

Add anti-CSRF tokens (nonces) to all forms and AJAX endpoints, and implement proper capability checks (current_user_can()) before executing privileged operations. Ensure all state-changing requests require valid authentication and authorization.

Recommended fix High confidence

7.3.10

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'AWeber – Free Sign Up Form and Landing Page Builder Plugin for Lead Generation and Email Newsletter Growth' plugin
  4. Click 'Update now' if an update is available, or manually download version 7.3.10 from the WordPress plugin repository
  5. After updating, verify the plugin version is 7.3.10 or higher in the plugins list
  6. Test that the plugin functionality works correctly after the update

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

Fix this in Aweber Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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