LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46776: WordPress Auto Excerpt everywhere Plugin <= 1.5 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Serena Villa Auto Excerpt everywhere plugin <= 1.5 versions.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity CSRF issue in the WordPress Auto Excerpt everywhere plugin. An attacker could potentially trick a logged-in user into triggering unintended plugin-related actions. The public sources do not describe the exact action, fixed version, or patch details, so owners should verify vendor guidance before assuming remediation is complete.

Executive priority

Treat this as a near-term WordPress exposure item. It is high severity, but current public evidence does not confirm active exploitation or a named fix. Prioritize inventory, version confirmation, and vendor-guided remediation.

Technical view

CVE-2023-46776 is a CWE-352 CSRF vulnerability affecting Serena Villa Auto Excerpt everywhere plugin, reported for versions up to 1.5. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no attacker privileges, and required user interaction. Public detail is limited.

Likely exposure

Exposure is likely limited to WordPress sites with the Auto Excerpt everywhere plugin installed, especially versions 1.5 or earlier. The provided affected-version metadata is sparse, so inventory confirmation is important.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. CSRF typically requires user interaction and a valid victim browser session, but the public record does not specify the vulnerable action.

Researcher notes

Public sources identify CSRF and CVSS impact but do not provide endpoint details, proof of concept, vulnerable request semantics, or fixed-version data. Avoid assuming exploitability beyond the CVE and Patchstack statements.

Mitigation direction

  • Identify all WordPress sites using Auto Excerpt everywhere.
  • Check the installed plugin version against version 1.5 or earlier.
  • Review the vendor or Patchstack page for current remediation guidance.
  • Disable or remove the plugin if no trusted fix is available.
  • Restrict administrative access and review WordPress security controls.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record exact plugin versions from production and staging systems.
  • Check Patchstack and CVE records for updated fixed-version information.
  • Review WordPress logs for suspicious plugin-setting changes.
  • Verify that any remediation was applied across all affected sites.
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-46776 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
8.8 (3.1)
Known Exploited
No
Published

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

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
Serena VillaAuto Excerpt everywhereauto-excerpt-everywhere, 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.