CVE-2025-32213: WordPress Flo Forms plugin <= 1.0.43 - 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.43.
Security readout for executives and security teams
Plain-English summary
Flo Forms for WordPress has a missing authorization issue affecting versions through 1.0.43. A logged-in, low-privileged user could reach data or functionality they should not access. The public record scores confidentiality impact as high, but does not describe the exact exposed data.
Executive priority
Treat as a normal-priority WordPress application risk, accelerated for sites collecting sensitive client, lead, or security-service information. It is not currently source-supported as actively exploited, but confidentiality impact makes timely remediation appropriate.
Technical view
CVE-2025-32213 is CWE-862 missing authorization in flothemesplugins Flo Forms flo-forms through 1.0.43. CVSS 3.1 is 6.5: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Likely exposure
Exposure is limited to WordPress sites with the Flo Forms plugin installed at version 1.0.43 or earlier. Risk is higher where low-privileged WordPress accounts are available to contractors, customers, subscribers, or other non-administrators.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation requires some authenticated low-privileged access, not anonymous access. Public details are sparse, so validation should avoid assumptions about the exact protected resource.
Researcher notes
Available public data identifies missing authorization and CVSS impact, but not the vulnerable endpoint, affected capability, or fixed version. Do not infer exploitability beyond authenticated low-privileged access and high confidentiality impact unless additional vendor or Patchstack detail confirms it.
Mitigation direction
Inventory WordPress sites for the Flo Forms plugin and installed version.
Check Patchstack and vendor guidance for a fixed release or official mitigation.
Upgrade if an official fixed version is available and compatible.
Disable or remove the plugin where it is not business-critical.
Reduce unnecessary low-privileged WordPress accounts until remediation is complete.
Validation and detection
Confirm whether each WordPress instance runs Flo Forms version 1.0.43 or earlier.
Review user roles for low-privileged accounts with access to affected sites.
Check application logs for unusual access to Flo Forms-related resources.
Verify remediation against vendor or Patchstack guidance before closing the finding.
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.
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.
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.
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.