WebCritical 9.8Patch available
CVE-2026-85097
Unauthenticated arbitrary file upload in Bricksforge WordPress plugin enabling RCE.
How scary is it?
updated 13 Oct 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list4
Not in the catalog as of our last sync.
Are you affected? only if all are true
You run Bricksforge in an affected version<= 3.1.8.9
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpdate plugin to fixed version, scan/remove web shells, restore from clean backup, rotate credentials
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 3.6%chance of exploitation in the next 30 daystop 11% of scored CVEsFIRST score of 22 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 8 Oct 2026analysed here 8 Oct 2026
Summary
Impact
Unauthenticated attacker can upload and execute PHP, achieving remote code execution, site takeover, backdoors, and data theft.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Bricksforge | <= 3.1.8.9Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- Bricksforge WordPress plugin <= 3.1.8.9
- WordPress sites using Bricksforge plugin
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? Partly. The vulnerability involves unauthenticated arbitrary file upload via the WordPress plugin, which occurs through HTTP requests containing file uploads. A WAF can partly detect this by matching unusual file upload patterns such as unexpected file types or names, but may not fully block all malicious uploads without affecting legitimate users. A custom WAF rule can filter file upload with arbitrary file type or name, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.
What a custom rule would match: file upload with arbitrary file type or name
Also consider: patch · custom WAF rule · MIME sniff · sandbox storage
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 5 GitHub proofs of concept · 1 Nuclei template
- CISA SSVC
- exploitation none, automatable yes, technical impact totalAssessed by CISA 8 Oct 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Nuclei
- Bricksforge WordPress Plugin <=3.1.8.9 - Unauthenticated Arbitrary File Uploaddetection template, critical
GitHub proofs of concept
- tc4dy/CVE-2026-85097-Toolkit6 stars
- Wayang1337/CVE-2026-850971 stars
- Masriyan/CVE-2026-850971 stars
- BlackHatExploitation/CVE-2026-850971 stars
and 1 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 8 Oct 2026Published
- 8 Oct 2026Analysed by vulneraibility.comsame day later
- 8 Oct 2026CISA SSVC assessment: exploitation nonesame day later
- 8 Oct 2026CVE record last updatedsame day later
- 10 Oct 2026First proof-of-concept repository on GitHub (unvetted)1 day later
Common questions
Is CVE-2026-85097 being exploited?
Not confirmed. CVE-2026-85097 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 3.6% probability of exploitation in the next 30 days.
How severe is CVE-2026-85097?
CVE-2026-85097 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-85097?
Yes. A fix has been recorded for CVE-2026-85097. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-85097 affect?
CVE-2026-85097 affects Bricksforge WordPress plugin <= 3.1.8.9, WordPress sites using Bricksforge plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-85097?
Update plugin to fixed version, scan/remove web shells, restore from clean backup, rotate credentials
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Other links (2)
- wordfence.com /threat-intel/vulnerabilities/id/e993c929-f175-43a7-92e6-9d3b089b8dde?source=cve
- bricksforge.io /version-changelog/
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.