vciy

CVE-2025-20075

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Server-side request forgery (SSRF) vulnerability exists in FileMegane versions above 3.0.0.0 prior to 3.4.0.0

CVE-2025-200753 of 4 sources documented this
18

rank 18 = 0 + 18 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00355  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.2, from the CNA  ·  without this subject the record ranks 0

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 18

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 18

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 18

Hindsight · the state

0.00355EPSSNOT IN KEVas of 2026-10-18
Severity7.2 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-02-18, 573 days at 0.00, as of 2026-09-14. arc-rules@v1

Foresight · where to check next

Microsoft Skypevrana adminerVMware vCenterCVE-2019-9621SonicWall SMA1000Configurator20075

This record is one instance of CWE-918, server-side request forgery (ssrf). The index holds 3924 prior instances of this class, 24 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running JIP InfoBridge Co., Ltd. FileMegane? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Watch JIP InfoBridge Co., Ltd. FileMegane

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactPartial confidentiality and availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.0 · the CNA's vectorreceipt
Weakness classCWE-918 Server-Side Request Forgery (SSRF)receipt
Published consequencesCWE-918: Confidentiality: Read Application Data; Integrity: Execute Unauthorized Code or Commands; Access Control: Bypass Protection Mechanismcwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 14 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.2 HIGHreceipt
Exploit probability0.00355 · top 72% of all CVEsreceipt
Assigned byjpcertreceipt
Recorded changes26 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productJIP InfoBridge Co., Ltd. FileMeganereceipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$7,580over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$7,580 = $4.99M incident cost x 0.42806422275080447 exposure x 0.00355 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Server-side request forgery (SSRF) vulnerability exists in FileMegane versions above 3.0.0.0 prior to 3.4.0.0. Executing arbitrary backend Web API requests could potentially lead to rebooting the services. receipt

NVD's analysis a second authority

weakness
CWE-918
also scored by
vultures@jpcert.or.jp 7.2 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L

check it yourself info-brdg.co.jp jvn.jp receipt

Movement the material steps

18 Feb 20250.00043
17 Mar 20250.0005 · scoring model v2025.03.14
15 Jun 20260.00327 · scoring model v2026.06.15
14 Sep 20260.00355
Show all 26 observations
18 Feb 20250.00043
17 Mar 20250.0005
21 Mar 20250.00054
29 Mar 20250.00046
30 Mar 20250.00054
26 Apr 20250.00057
19 Jun 20250.00078
12 Jul 20250.00045
17 Jul 20250.00051
28 Jul 20250.0006
13 Sep 20250.00064
23 Sep 20250.00072
23 Oct 20250.00078
3 Nov 20250.00083
13 Nov 20250.00085
18 Nov 20250.00147
21 Nov 20250.00085
4 Dec 20250.00092
14 Dec 20250.00102
24 Mar 20260.0016
29 Mar 20260.00047
31 Mar 20260.00075
15 Jun 20260.00327
16 Jul 20260.00342
20 Aug 20260.00348
14 Sep 20260.00355

26 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00355Published2025-02-17Index as of2026-09-14

The record had been public for 1 year, 6 months when this index was last written.

Published 2025-02-17 receipt · Index as of 2026-09-14 derived

The pattern, elsewhere

This record is one instance of CWE-918, server-side request forgery (ssrf). The index holds 3924 prior instances of this class, 24 KEV-listed. The nearest of its KEV-listed records are drawn beside this. cwe-consequences@4.20

CVE-2023-41763 · Microsoft Skype for Business Server 2015 CU13matches 6 of 9KEV listed · 2023receipt
CVE-2021-21311 · vrana adminermatches 6 of 9KEV listed · 2021receipt
CVE-2021-21973 · VMware vCenter Servermatches 6 of 9KEV listed · 2021receipt
CVE-2019-9621matches 5 of 8KEV listed · 2019receipt
CVE-2026-15409 · SonicWall SMA1000matches 5 of 9KEV listed · 2026receipt
CVE-2025-61884 · Oracle Configuratormatches 5 of 9KEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

3924 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2025-20075.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.