LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23711: WordPress A2 Optimized WP Plugin <= 3.0.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in A2 Hosting A2 Optimized WP plugin <= 3.0.4 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the A2 Optimized WP WordPress plugin in versions up to 3.0.4. It is a CSRF issue, meaning a logged-in user could be tricked into making an unintended change. The known impact is limited integrity impact, not data theft or service outage.

Executive priority

Handle during normal vulnerability remediation unless the plugin protects high-value or frequently administered sites. There is no supplied evidence of active exploitation, but vulnerable WordPress admin workflows can still create business risk through unauthorized configuration changes.

Technical view

CVE-2023-23711 is a CWE-352 CSRF vulnerability in A2 Hosting A2 Optimized WP, reported for plugin versions <= 3.0.4. CVSS 3.1 is 4.3 with network attack vector, low complexity, required user interaction, no confidentiality impact, low integrity impact, and no availability impact.

Likely exposure

Exposure is likely limited to WordPress sites with the A2 Optimized WP plugin installed at version 3.0.4 or earlier. The source bundle does not identify affected endpoints, configurations, or hosting requirements beyond the plugin and version range.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not marked KEV. CVSS indicates exploitation requires user interaction. Treat this as a targeted integrity risk against vulnerable WordPress administrative workflows, not as evidence of broad exploitation.

Researcher notes

Available sources identify CSRF class, affected plugin, version boundary, CWE, and CVSS. They do not provide endpoint-level details, proof-of-concept status, exploit telemetry, or a named fixed version. Avoid assuming exploitability beyond user-interaction-based integrity impact.

Mitigation direction

  • Inventory WordPress sites for the a2-optimized-wp plugin and version.
  • Check A2 Hosting and Patchstack guidance for a fixed version or official mitigation.
  • Update, disable, or remove vulnerable installations where vendor guidance supports that action.
  • Reduce unnecessary administrator sessions on affected sites until remediation is complete.

Validation and detection

  • Confirm whether A2 Optimized WP is installed on each WordPress site.
  • Record the installed plugin version and compare it to <= 3.0.4.
  • Review vulnerability scanner results for CVE-2023-23711 or the a2-optimized-wp slug.
  • After remediation, verify 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-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-23711 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-23711Attack 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
A2 HostingA2 Optimized WPa2-optimized-wp, 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.