LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52149: WordPress Floating Button Plugin <= 6.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Wow-Company Floating Button.This issue affects Floating Button: from n/a through 6.0.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52149 is a CSRF flaw in the Wow-Company Floating Button WordPress plugin through version 6.0. An attacker could potentially cause unwanted site changes if a logged-in user is tricked into interacting with malicious content. The public sources rate it medium severity, not an emergency-level issue.

Executive priority

Treat this as a routine but real website hygiene issue. Prioritize internet-facing WordPress properties using the plugin, especially business-critical sites, but do not escalate as an active-exploitation emergency based on the provided evidence.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in the WordPress Floating Button plugin, package floating-button, through 6.0. CVSS 3.1 is 5.4 with network attack vector, low complexity, required user interaction, and low integrity and availability impact. The provided sources do not name a specific patched version or detailed fix.

Likely exposure

Exposure is limited to WordPress sites running Wow-Company Floating Button version 6.0 or earlier. Sites not using this plugin, or using versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not support active exploitation. Exploitation would require user interaction, consistent with the CVSS UI:R rating. Public evidence is incomplete on real-world abuse, exploit maturity, and exact vulnerable request behavior.

Researcher notes

Key constraints are CVSS UI:R and low integrity/availability impact. The bundle identifies affected versions through 6.0 but does not provide endpoint details, nonce behavior, proof-of-concept material, or a named patched version. Avoid assuming exploitation or remediation specifics beyond vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the floating-button plugin and version.
  • Check Wow-Company and Patchstack guidance for a fixed release or vendor mitigation.
  • Update the plugin if a fixed vendor version is available.
  • Disable or remove the plugin where it is unnecessary or cannot be updated.
  • Limit privileged WordPress sessions and reinforce administrator phishing precautions.

Validation and detection

  • Confirm whether each WordPress site has floating-button installed.
  • Record plugin versions and flag version 6.0 or earlier.
  • Review WordPress change logs for unexpected Floating Button configuration changes.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
  • Document any sites awaiting vendor guidance as residual risk.
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-52149 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-52149Attack 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
Wow-CompanyFloating Buttonfloating-button, n/aunaffected
Weakness

CWE details

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