LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0088: Swifty Page Manager <= 3.0.1 - Cross-Site Request Forgery

The Swifty Page Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.0.1. This is due to missing or incorrect nonce validation on several AJAX actions handling page creation and deletion among other things. This makes it possible for unauthenticated attackers to invoke those functions, via forged request granted they can trick a site administrator into performing an action such as clicking on a link.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-0088 affects the Swifty Page Manager WordPress plugin through version 3.0.1. A malicious site or link could cause a logged-in administrator’s browser to trigger plugin actions, including page creation or deletion, because nonce checks were missing or incorrect.

Executive priority

Treat this as high priority for WordPress sites that use the plugin, especially public sites with multiple administrators. The attack depends on administrator interaction, but successful abuse can alter or remove site content.

Technical view

The issue is CWE-352 cross-site request forgery in several Swifty Page Manager AJAX actions. The CVSS 3.1 score is 8.8 because the actions can affect confidentiality, integrity, and availability, but exploitation requires administrator interaction.

Likely exposure

Exposure is limited to WordPress sites using Swifty Page Manager up to and including 3.0.1. The supplied affected metadata appears inconsistent, so verify installed plugin versions directly.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Abuse requires tricking a site administrator into performing an action, such as clicking a link, while their session can authorize the forged request.

Researcher notes

The strongest evidence is Wordfence’s advisory and the referenced WordPress plugin source. The CVE record’s affected metadata is sparse and conflicts with the narrative range, so do not rely on CPE matching alone.

Mitigation direction

  • Inventory WordPress sites for Swifty Page Manager and installed versions.
  • Check vendor and Wordfence guidance for a fixed release or official remediation.
  • Disable or remove the plugin where no supported fix is available.
  • Limit administrator exposure to untrusted links and external browsing.
  • Review recent page creation and deletion activity for unauthorized changes.

Validation and detection

  • Confirm whether Swifty Page Manager is installed on each WordPress instance.
  • Record the plugin version and compare it with the <= 3.0.1 affected range.
  • Review plugin AJAX handlers for proper nonce validation.
  • Check site logs and content history for unexpected page changes.
  • Confirm compensating action after update, removal, or vendor-directed remediation.
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-0088 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-0088Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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
swiftylifeSwifty Page Manager0unaffected
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.