Arigato Autoresponder And NewsletterWordPress extension · Kibokolabs
CVE-2023-25020
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 · uneditedUnauth. Stored Cross-Site Scripting (XSS) vulnerability in Kiboko Labs Arigato Autoresponder and Newsletter plugin <= 2.7.1.1 versions.
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 confidenceUnauthenticated stored Cross-Site Scripting (XSS) vulnerability in Kiboko Labs Arigato Autoresponder and Newsletter WordPress plugin versions 2.7.1.1 and below allows attackers to inject malicious JavaScript that persists and executes in browsers of users viewing compromised content.
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
Arigato Autoresponder And NewsletterWordPress extension
<= 2.7.1.1CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedCheck WordPress admin under Plugins > Installed Plugins, or use command: wp plugin list --search='arigato'Affected if The Kiboko Labs Arigato Autoresponder and Newsletter plugin appears in the list of installed plugins
-
Identify installed versionView plugin details in WordPress admin plugins list, or read version from plugin header file: wp-content/plugins/arigato-autoresponder/arigato-autoresponder.phpAffected if The displayed version is 2.7.1.1 or lower (any version up to and including 2.7.1.1)
-
Verify plugin is activeCheck if the plugin status shows as 'Active' in WordPress admin Plugins page, or run: wp plugin status arigato-autoresponderAffected if The plugin is currently activated on the site
-
Confirm public-facing functionality is accessibleVisit pages where the plugin's newsletter signup or subscription forms are rendered (typically pages with /newsletter/ or /subscribe/ in the URL, or any endpoint that processes the plugin's form submissions)Affected if The plugin's subscription or autoresponder forms are accessible to unauthenticated visitors
A site is affected if it has the Arigato Autoresponder and Newsletter plugin installed with version 2.7.1.1 or below and the plugin is active with its public forms accessible.
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 Arigato Autoresponder and Newsletter plugin to the latest version; if no patched version is available, remove the plugin until a fix is released.
Fix this in Arigato Autoresponder And Newsletter
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25020 — 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-2023-25020 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