LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6137: WordPress Frontier Post Plugin <= 6.1 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in finnj Frontier Post allows Cross Site Request Forgery.This issue affects Frontier Post: from n/a through 6.1.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-6137 is a CSRF issue in the WordPress Frontier Post plugin through version 6.1. A victim must interact with attacker-controlled content, and the public sources do not describe the exact action affected. Business impact is limited but real: unauthorized changes or disruption may be possible on sites using the plugin.

Executive priority

Treat this as a moderate WordPress plugin risk. It should be handled in routine vulnerability remediation, with faster action for public sites, heavily used publishing workflows, or sites where many privileged users manage content.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in finnj Frontier Post, package frontier-post, affecting versions through 6.1. CVSS 3.1 is 5.4 with network access, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact. No confidentiality impact is indicated.

Likely exposure

Exposure is likely limited to WordPress sites with Frontier Post installed and active at version 6.1 or earlier. Sites without this plugin are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. Exploitation requires user interaction, consistent with CSRF, but the public details provided do not identify the vulnerable request, role, endpoint, or action.

Researcher notes

Evidence is sparse. The bundle identifies CSRF, affected versions through 6.1, CVSS 5.4, and Patchstack as the vulnerability database reference. It does not provide endpoint-level details, proof of concept status, observed exploitation, or a named fixed version.

Mitigation direction

  • Inventory WordPress sites for the Frontier Post plugin and its installed version.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Upgrade the plugin if a vendor-supported fixed version is available.
  • Disable or remove the plugin where no supported fix is available.
  • Limit administrative sessions and review high-privilege WordPress access.

Validation and detection

  • Confirm whether frontier-post is installed and active on each WordPress site.
  • Record plugin versions and flag any version through 6.1.
  • Review vendor and Patchstack records for fixed-version guidance.
  • Check recent site changes for unexpected post-management activity.
  • Document compensating controls if removal or upgrade is delayed.
Prepared
Confidence
high
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-6137 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-6137Attack 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
finnjFrontier Postfrontier-post, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.