NVD / CVE Program· CNA Microchip

CVE-2025-47902: SQL Injection in web resource

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
Someone on the same network segment can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Microchip Time Provider 4100 2.5.

Low priority for now. Upgrade to Microchip Time Provider 4100 2.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Microchip Time Provider 4100 allows SQL Injection.This issue affects Time Provider 4100: before 2.5.

HighCVSS 7.1 · v4.0—No exploit Fix available

SQL injection

Published: Oct 20, 2025
Updated: Oct 8, 2026
EPSS: 0.3% · 31th percentile
CWE: CWE-89

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Microchip: 7.1; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
microchip	timeprovider 4100 firmware	cpe:2.3:o:microchip:timeprovider_4100_firmware
microchip	timeprovider 4100	cpe:2.3:h:microchip:timeprovider_4100

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

microchip timeprovider 4100 firmwarebefore 2.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Microchip). Independent of NVD's CPE analysis and usually ahead of it.

Microchip Time Provider 4100
- before 2.5affected · semver

Same product

microchip: all records

Other highest-scoring records for the same primary product.

CVE-2024-9054Remote code Execution inTimeProvider® 4100
39Monitor
CVE-2025-47901RCE on restore configuration password
35Monitor
CVE-2025-47900RCE on backup configuration password
35Monitor

Published before and after this one in the same product

← EarlierCVE-2024-43687Oct 4, 2024 · XSS vulnerability in bannerconfig endpoint in TimeProvider 4100
30Monitor
← EarlierCVE-2024-7801Oct 4, 2024 · SQL injection in get_chart_data in TimeProvider 4100
25Monitor
Later →CVE-2025-47904Feb 24, 2026 · Unsigned upgrade package
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Microchip Time Provider 4100	2.5	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Antonio Carrierofinder
Dario Emilio Bertanifinder
Andrea Sindonifinder
Marco Manierifinder
Vito Pistillofinder
Davide Rennafinder
Manuel Leonefinder
Massimiliano Brollifinder
TIM Security Red Team Research (TIM S.p.A)reporter
Raffaele BovaNozomi Networksfinder
Simone BossiNozomi Networksfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-7801381 days apartSQL injection in get_chart_data in TimeProvider 4100
25Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone on the same network segment can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Adjacent
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = '" + owner + "'"
4);

Fixed

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = $1",
4  [owner]
5);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.gruppotim.it/en/footer/TIM-red-team.html

Show all references (1 more)

www.microchip.com/en-us/solutions/technologies/embedded-security/how-to-report-potential-product-security-vulnerabilities/timeprovider-4100-grandmaster-remote-sql-command-injection-47902

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records