LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25020: WordPress Arigato Autoresponder and Newsletter Plugin <= 2.7.1.1 is vulnerable to Cross Site Scripting (XSS)

Unauth. Stored Cross-Site Scripting (XSS) vulnerability in Kiboko Labs Arigato Autoresponder and Newsletter plugin <= 2.7.1.1 versions.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using Kiboko Labs Arigato Autoresponder and Newsletter up to 2.7.1.1. An unauthenticated attacker may store malicious script that runs when another user interacts with affected content. That can expose user data, alter page behavior, or disrupt trust in the site.

Executive priority

Treat this as a high-priority WordPress plugin exposure review. It is not confirmed as actively exploited in the supplied sources, but unauthenticated stored XSS on public sites can create reputational, account, and data-risk consequences.

Technical view

CVE-2023-25020 is an unauthenticated stored XSS in the WordPress plugin bft-autoresponder, mapped to CWE-79. CVSS 3.1 is 7.1 with network access, low complexity, no privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress installations running Arigato Autoresponder and Newsletter versions 2.7.1.1 or earlier. Public-facing WordPress sites are the primary concern, especially where newsletter or autoresponder functions accept unauthenticated input.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The vulnerability is still business-relevant because stored XSS can persist until removed and may affect administrators or visitors who view the affected content.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The bundle does not include a fixed version, exploit proof, or detailed vulnerable parameter information, so validation should stay version- and exposure-based unless official vendor details are available.

Mitigation direction

  • Inventory WordPress sites for Arigato Autoresponder and Newsletter plugin use.
  • Check vendor or Patchstack guidance for a fixed version or official workaround.
  • If no fix is available, disable or remove the plugin where feasible.
  • Prioritize public-facing sites and administrator-accessible affected content.
  • Review stored newsletter or autoresponder content for unexpected script-like content.

Validation and detection

  • Confirm plugin slug bft-autoresponder and installed version across WordPress assets.
  • Flag installations running version 2.7.1.1 or earlier.
  • Check whether unauthenticated users can submit affected newsletter or autoresponder content.
  • Review site logs and content records for suspicious submissions around vulnerable workflows.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-25020 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-25020Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Kiboko LabsArigato Autoresponder and Newsletterbft-autoresponder, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.