LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47686: WordPress Arigato Autoresponder and Newsletter Plugin <= 2.7.2.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Kiboko Labs Arigato Autoresponder and Newsletter plugin <= 2.7.2.2 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47686 is a medium-severity CSRF flaw in the WordPress Arigato Autoresponder and Newsletter plugin through version 2.7.2.2. An attacker would need to trick a user into taking an action, and the documented impact is limited integrity change. The sources do not describe the exact affected action.

Executive priority

Treat as a routine but time-bound WordPress plugin remediation. Business urgency is lower than unauthenticated remote code execution, but exposed marketing or newsletter workflows can still be altered if a privileged user is tricked.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in Kiboko Labs Arigato Autoresponder and Newsletter, package bft-autoresponder, affecting versions <= 2.7.2.2. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites that have the Arigato Autoresponder and Newsletter plugin installed at version 2.7.2.2 or earlier. Sites without this plugin, or using versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as CISA KEV, and the provided sources do not state active exploitation. CSRF generally depends on social engineering a legitimate user, but the source bundle does not identify the exact victim role, request, or workflow involved.

Researcher notes

Available evidence is sparse: no affected endpoint, nonce failure detail, proof of concept, patch version, or exploitation report is included in the provided sources. Validate only with authorized, non-destructive review of version state and vendor advisory details.

Mitigation direction

  • Inventory WordPress sites for the bft-autoresponder plugin and record installed versions.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • If running <= 2.7.2.2, update, replace, or disable according to vendor guidance.
  • Reduce unnecessary WordPress administrative access until remediation is confirmed.

Validation and detection

  • Confirm whether Arigato Autoresponder and Newsletter is installed on each WordPress site.
  • Verify the installed plugin version is greater than 2.7.2.2 or otherwise vendor-confirmed safe.
  • Review WordPress admin activity for unexpected newsletter or autoresponder configuration changes.
  • Track remediation evidence in vulnerability management records.
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-352: 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-47686 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-47686Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.