CVE
Looks Awesome Flow-Flow Social Stream unauthenticated sensitive data exposure in public files
Affects the Flow-Flow Social Stream WordPress plugin by Looks Awesome, versions 5.0.5 and earlier. Fixed in 5.0.8.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 5.0.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.0.8.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.24% · 15th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The Flow-Flow Social Stream plugin for WordPress, from Looks Awesome, contains a flaw that lets an attacker remotely, without logging in, retrieve sensitive data embedded in externally accessible files or directories. The attacker gains read access to that confidential information.
Original description
Insertion of Sensitive Information into Externally-Accessible File or Directory vulnerability in Looks Awesome Flow-Flow Social Stream flow-flow-social-streams allows Retrieve Embedded Sensitive Data.This issue affects Flow-Flow Social Stream: from n/a through 5.0.5.
Who should check
Sites and teams running the Flow-Flow Social Stream WordPress plugin version 5.0.5 or earlier.
“<= 5.0.5 Vulnerable version(s)”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.0.8.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125799 (WordPress Flow-Flow Social Stream plugin <= 5.0.5 - Sensitive Data Exposure vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125799 (entry last updated 2026-11-16):
Affected:
- Looks Awesome Flow-Flow Social Stream: through 5.0.5
Fixed versions: 5.0.8.
Conditions (all must be true for the bug to be hit):
- Plugin version 5.0.5 or earlier (vulnerable versions <= 5.0.5). (source: https://patchstack.com/database/wordpress/plugin/flow-flow-social-streams/vulnerability/wordpress-flow-flow-social-stream-plugin-5-0-5-sensitive-data-exposure-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-125799 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125799 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/flow-flow-social-streams/vulnerability/wordpress-flow-flow-social-stream-plugin-5-0-5-sensitive-data-exposure-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-125799
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125799
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125799"}.Timeline
- CVE published
- First seen by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- flow-flow-social-streams
through 5.0.5
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125799
Is CVE-2026-125799 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin can expose private information such as passwords, emails, or payment details to unauthorized parties.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-125799?
flow-flow-social-streams: through 5.0.5.Source: cve.now feed data
Am I affected, and how do I check?
The plugin versions 5.0.5 and earlier are affected. The installed version can be checked on the WordPress Plugins screen, where the Flow-Flow Social Stream version is listed.Source: patchstack.com, cve.org
How do I fix CVE-2026-125799?
Update the Flow-Flow Social Stream plugin to the latest available version, which must be at least 5.0.8.Source: patchstack.com, cve.org