LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36517: WordPress WP Abstracts Plugin <= 2.6.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Kevon Adonis WP Abstracts plugin <= 2.6.2 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-36517 is a CSRF issue in the WordPress WP Abstracts plugin through version 2.6.2. If a logged-in user can be tricked into a malicious interaction, an attacker may cause a limited unwanted change. Business impact is moderate and mainly integrity-related, not data theft or outage based on the supplied CVSS data.

Executive priority

Treat this as a scheduled remediation item for affected WordPress sites, not an emergency, unless WP Abstracts supports sensitive workflows or privileged administrators use it frequently.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in Kevon Adonis WP Abstracts, package wp-abstracts-manuscripts-manager, affecting versions <= 2.6.2. CVSS 3.1 is 4.3 with network attack vector, low complexity, no privileges required, user interaction required, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running WP Abstracts version 2.6.2 or earlier. Sites without this plugin, or running unaffected versions, are not indicated as exposed by the provided data.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction, likely involving a logged-in WordPress user being induced to perform an unintended request.

Researcher notes

Evidence supports CSRF with limited integrity impact only. No exploit details, fixed version, or official mitigation is included in the supplied bundle, so validation should focus on plugin presence, version, and vendor advisory status.

Mitigation direction

  • Inventory WordPress sites for the WP Abstracts plugin and record installed versions.
  • Check vendor, WordPress plugin, and Patchstack guidance for a fixed release or official workaround.
  • Upgrade or replace affected plugin versions when a vendor-supported fix is available.
  • Temporarily disable WP Abstracts where it is not business-critical.
  • Review administrative access hygiene and reduce unnecessary privileged WordPress sessions.

Validation and detection

  • Confirm whether wp-abstracts-manuscripts-manager is installed on each WordPress site.
  • Flag installations running WP Abstracts version 2.6.2 or earlier.
  • Verify whether a vendor-supported fixed version has been applied before closing the finding.
  • Review WordPress activity logs for unexpected WP Abstracts configuration or content changes.
  • Monitor CVE, Patchstack, and vendor sources for exploitation or remediation updates.
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-36517 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-36517Attack 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
Kevon AdonisWP Abstractswp-abstracts-manuscripts-manager, 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.