WordPress Zoho Flow plugin <= 2.14.5 - PHP Object Injection vulnerability
Affects the WordPress Zoho Flow plugin version 2.14.5 and earlier. No fixed version is listed in the checked facts, and no vendor rating is given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts do not describe a workaround. No mitigation steps are documented in the sources reviewed, so none can be recommended from them.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.31% · 24th 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? →
- 35/100
- 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: total
Summary
Unauthenticated PHP Object Injection in Zoho Flow <= 2.14.5 versions.
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
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts do not describe a workaround. No mitigation steps are documented in the sources reviewed, so none can be recommended from them.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- zoho-flow
through 2.14.5
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62131
Is CVE-2026-62131 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 flaw is a PHP Object Injection issue. It lets attackers manipulate how the site processes data so that harmful actions run on the server.Source: patchstack.com
Which versions are affected by CVE-2026-62131?
zoho-flow: through 2.14.5.Source: cve.now feed data
Am I affected, and how do I check?
The WordPress Zoho Flow plugin, version 2.14.5 and earlier, is listed as affected. To check the installed version, look at the plugin's version number in the WordPress admin Plugins screen.Source: patchstack.com
How do I fix CVE-2026-62131?
The checked facts do not name a fixed version, so no upgrade target can be confirmed. Watch for a plugin release newer than 2.14.5 and install it once the vendor publishes it.Source: patchstack.com
What if there's no patch?
The checked facts do not describe a workaround. No mitigation steps are documented in the sources reviewed, so none can be recommended from them.Source: patchstack.com