LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3248: All-in-one Floating Contact Form < 2.1.2 - Admin+ Stored Cross-Site Scripting

The All-in-one Floating Contact Form WordPress plugin before 2.1.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects a WordPress contact/social tabs plugin before 2.1.2. A highly privileged user, such as an admin, could store script content in plugin settings where it should have been sanitized. Business urgency is moderate because exploitation requires admin-level access and user interaction, but it can bypass HTML restrictions in multisite environments.

Executive priority

Treat as a moderate-priority hygiene fix. It is unlikely to be an unauthenticated takeover path, but it can undermine WordPress security controls and create stored browser-side risk where privileged accounts are compromised or misused.

Technical view

CVE-2023-3248 is stored cross-site scripting in All-in-one Floating Contact Form, Call, Chat, and 50+ Social Icon Tabs before 2.1.2. Some settings were not sanitized and escaped. CVSS 3.1 is 4.8 with network access, low complexity, high privileges, required user interaction, changed scope, and low confidentiality/integrity impact.

Likely exposure

Exposure is limited to WordPress sites running the affected plugin below version 2.1.2. The most relevant scenario is multisite or hardened deployments where admins do not have unfiltered_html, because this flaw weakens that intended restriction.

Exploitation context

The bundle lists a WPScan reference tagged as exploit, but KEV is false and no cited source confirms active exploitation. The attacker must already hold high privilege, and successful impact depends on stored content later being rendered to a user.

Researcher notes

Evidence is narrow but consistent: CWE-79, stored XSS, high privileges required, and affected versions before 2.1.2. The provided affected metadata is sparse, so avoid expanding affected products beyond the named WordPress plugin.

Mitigation direction

  • Update the plugin to version 2.1.2 or later.
  • Check vendor and WPScan guidance for any additional remediation notes.
  • Restrict administrator access to trusted users only.
  • Review multisite admin policies where unfiltered_html is intentionally disabled.

Validation and detection

  • Inventory WordPress sites for the affected plugin.
  • Confirm installed plugin versions are 2.1.2 or later.
  • Review plugin settings for unexpected script-like content.
  • Check recent admin changes on affected WordPress sites.
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-79: 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-3248 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
4.8 (3.1)
Known Exploited
No
Published

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

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
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.8Medium
CVSS 3.1 vector shape for CVE-2023-3248Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownAll-in-one Floating Contact Form, Call, Chat, and 50+ Social Icon Tabs0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.