LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0403: Social Warfare <= 4.3.1 - Cross-Site Request Forgery

The Social Warfare plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.3.1. This is due to missing or incorrect nonce validation on several AJAX actions. This makes it possible for unauthenticated attackers to delete post meta information and reset network access tokens, via forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites running Social Warfare up to 4.3.1. A malicious site or link could cause a logged-in administrator to unknowingly trigger plugin actions, potentially deleting post metadata or resetting network access tokens.

Executive priority

Treat as a routine but real WordPress hygiene issue. It is not described as actively exploited, but affected public sites should be upgraded or the plugin removed during normal patch cycles.

Technical view

CVE-2023-0403 is a CSRF flaw caused by missing or incorrect nonce validation on several Social Warfare AJAX actions. It is remotely reachable but requires user interaction by a site administrator. Reported impact is limited integrity and availability loss.

Likely exposure

Exposure is limited to WordPress installations with the Social Warfare plugin at version 4.3.1 or earlier. Sites without the plugin, or on versions not covered by the advisory, are not shown as affected by the provided sources.

Exploitation context

The source bundle does not indicate CISA KEV listing or active exploitation. Abuse depends on tricking an authenticated administrator into performing an action, such as clicking a crafted link.

Researcher notes

Key evidence is Wordfence’s advisory and the referenced WordPress plugin source location. The CVE data names CSRF, CWE-352, CVSS 5.4, unauthenticated attacker initiation, and administrator interaction as required conditions.

Mitigation direction

  • Identify all WordPress sites running Social Warfare.
  • Check vendor or WordPress plugin guidance for the fixed current release.
  • Upgrade affected installations beyond version 4.3.1 where vendor guidance supports it.
  • Disable or remove the plugin if no supported fix is available.
  • Limit administrator browsing from authenticated WordPress sessions where practical.

Validation and detection

  • Confirm whether Social Warfare is installed on each WordPress site.
  • Record the installed plugin version and compare it to 4.3.1.
  • Review vendor release notes or advisory status for fixed versions.
  • Verify administrative AJAX actions enforce nonce validation after remediation.
  • Check for unexpected post metadata changes or reset social network tokens.
Prepared
Confidence
high
Sources
4

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-0403 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
4Source 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-0403Attack 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
warfarepluginsSocial Sharing Plugin – Social Warfare0unaffected
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.