LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23719: WordPress Premmerce Plugin <= 1.3.17 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Premmerce plugin <= 1.3.17 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress Premmerce plugin through version 1.3.17. A CSRF flaw could let an attacker trick a logged-in user into triggering an unintended plugin-related action. The source bundle rates it medium, with limited integrity and availability impact and no confidentiality impact stated.

Executive priority

Treat this as a moderate website-platform risk. It is not cited as actively exploited, but affected WordPress sites should be identified and remediated through vendor guidance because admin interaction could lead to unwanted site changes.

Technical view

CVE-2023-23719 is a CWE-352 Cross-Site Request Forgery issue in the Premmerce WordPress plugin <= 1.3.17. CVSS 3.1 is 5.4 with network attack vector, low complexity, no privileges required, and required user interaction. The provided sources do not describe the vulnerable endpoint, patch version, or specific impact path.

Likely exposure

Exposure is limited to WordPress sites running the Premmerce plugin at version 1.3.17 or earlier. Sites without the plugin, or with versions outside the vulnerable range, are not indicated as affected by the provided sources.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation would require user interaction, likely involving a logged-in WordPress user being induced to make an unintended request. No exploit details are provided in the sources.

Researcher notes

Evidence is sparse. The source bundle confirms CSRF, affected plugin range, CWE, and CVSS, but not the vulnerable action, nonce/auth control failure, fixed version, or exploit maturity. Avoid assuming impact beyond limited integrity and availability effects stated by CVSS.

Mitigation direction

  • Inventory WordPress sites for the Premmerce plugin and installed version.
  • Check Premmerce and Patchstack guidance for a vendor-confirmed fixed release.
  • Update only to a vendor-confirmed fixed version when available.
  • Disable or remove Premmerce where it is not business-required.
  • Prioritize admin-user awareness until vendor guidance is confirmed.

Validation and detection

  • Confirm whether Premmerce is installed on each WordPress site.
  • Verify whether the installed version is 1.3.17 or earlier.
  • Check vendor or Patchstack records for current remediation guidance.
  • Review WordPress administrative activity for unexpected plugin-related changes.
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-23719 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
5.4 (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:L

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

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-23719Attack 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:L

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
PremmercePremmercepremmerce, 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.