CVE-2025-64273
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 · uneditedMissing Authorization vulnerability in GetResponse Email marketing for WordPress by GetResponse Official getresponse-official allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Email marketing for WordPress by GetResponse Official: from n/a through <= 1.5.3.
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 confidenceThe GetResponse Email Marketing WordPress plugin versions through 1.5.3 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This authorization bypass likely affects specific plugin endpoints or functions that fail to verify user permissions before performing sensitive operations.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed plugin versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate GetResponse Email Marketing, and note the version number displayed. Alternatively, use wp-cli: `wp plugin list --name='getresponse-email-marketing'` or inspect the plugin header in wp-content/plugins/getresponse-email-marketing/getresponse.phpAffected if The version listed is 1.5.3 or any version lower (e.g., 1.5.2, 1.5.1, 1.0.0)
-
Confirm plugin is activeCheck the Plugins page in WordPress admin - the GetResponse Email Marketing plugin must have an 'Active' status, or run `wp plugin status getresponse-email-marketing` via wp-cliAffected if The plugin is installed AND active (an inactive plugin would not expose its endpoints)
-
Review accessible plugin endpointsAudit publicly accessible URLs under /wp-json/getresponse/ or wp-admin/admin-ajax.php?action=getresponse* using a site crawler or by reviewing the plugin source files in wp-content/plugins/getresponse-email-marketing/ for registered REST routes and AJAX handlersAffected if Any GET or POST requests to plugin-specific URLs do not enforce capability checks (like 'manage_options') before performing actions
If the GetResponse Email Marketing plugin is installed at version 1.5.3 or earlier and is actively running, the missing authorization vulnerability is present and specific endpoints can likely be accessed without proper permission verification.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the GetResponse Email Marketing plugin to the latest version that includes proper authorization controls. If no update is available, restrict access to vulnerable endpoints via server-side configuration or implement application-level access control checks.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-64273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64273 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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