LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23721: WordPress Admin Log Plugin <= 1.50 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in David Gwyer Admin Log plugin <= 1.50 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-23721 is a CSRF issue in the WordPress Admin Log plugin through version 1.50. An attacker could trick a logged-in user into making an unintended plugin-related change. The expected impact is limited integrity impact, not data theft or service outage based on the CVSS vector.

Executive priority

Treat this as a moderate WordPress hygiene issue, not an emergency based on current evidence. Address it in the next normal vulnerability cycle, faster for sensitive public sites or environments with many administrators.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in David Gwyer Admin Log for WordPress, affecting versions <= 1.50. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is likely limited to WordPress sites with the Admin Log plugin package admin-log installed at version 1.50 or earlier and active. Risk depends on whether a user with relevant WordPress permissions can be induced to trigger a forged request.

Exploitation context

The provided bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates exploitation requires user interaction and affects integrity only. Public detail is limited, so avoid assuming a working exploit or broader impact.

Researcher notes

Available sources identify the weakness class, affected plugin, version boundary, and CVSS vector, but do not provide remediation detail or exploitation evidence in the bundle. Validation should focus on asset inventory, plugin state, version confirmation, and vendor guidance tracking.

Mitigation direction

  • Inventory WordPress sites for the Admin Log plugin and installed version.
  • Check vendor or Patchstack guidance for any fixed or recommended version.
  • If no trusted fix is available, consider disabling the plugin where nonessential.
  • Restrict administrative access to trusted users and hardened browsers.
  • Prioritize remediation on externally administered or high-value WordPress sites.

Validation and detection

  • Confirm whether package admin-log is installed and active on each WordPress site.
  • Record exact plugin versions and flag versions 1.50 or earlier.
  • Review vendor and Patchstack entries for remediation status before closure.
  • Check recent administrative activity for unexpected plugin-related changes.
  • Document compensating controls if the plugin cannot be removed quickly.
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-23721 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-23721Attack 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
David GwyerAdmin Logadmin-log, 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.