LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47692: WordPress Flo Forms plugin <= 1.0.41 - Broken Access Control vulnerability

Missing Authorization vulnerability in flothemesplugins Flo Forms flo-forms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Flo Forms: from n/a through <= 1.0.41.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47692 is a broken access control issue in the WordPress Flo Forms plugin through version 1.0.41. An authenticated user may be able to perform an action they should not be authorized to perform, creating limited integrity risk rather than data theft or outage risk.

Executive priority

Treat this as a moderate WordPress hygiene issue. Prioritize remediation on public sites with many authenticated users or customer portals, but it is below vulnerabilities enabling unauthenticated takeover, data theft, or service disruption.

Technical view

The issue is classified as missing authorization (CWE-862) in flothemesplugins Flo Forms package flo-forms. CVSS 3.1 is 4.3/Medium: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running Flo Forms versions up to and including 1.0.41, especially where untrusted or low-privileged authenticated accounts exist. The source bundle does not identify affected endpoints, roles, or exact unauthorized actions.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates exploitation requires authenticated low-privilege access, with no user interaction and limited integrity impact.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. No exploit, affected endpoint, fixed version, or vendor patch details are provided in the bundle. Avoid assuming unauthenticated exploitation because CVSS specifies PR:L.

Mitigation direction

  • Inventory WordPress sites for the Flo Forms plugin and record installed versions.
  • If Flo Forms is unused, disable or remove it until risk is resolved.
  • Check Patchstack and vendor guidance for a fixed version or official mitigation.
  • Limit WordPress accounts to necessary roles and remove stale authenticated users.
  • Monitor for unexpected form, plugin, or configuration changes.

Validation and detection

  • Confirm whether flo-forms is installed on each WordPress property.
  • Verify installed Flo Forms versions are not 1.0.41 or earlier.
  • Review WordPress user roles for low-privilege accounts with plugin access.
  • Check audit logs for unexpected Flo Forms changes.
  • Track the CVE and Patchstack entry for updated remediation details.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-47692 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
flothemespluginsFlo Formsflo-forms, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.