CVE Intelligence
Skip to main content
HIGH

CVE-2025-7051

CVE-2025-7051 — N-central Syslog Configuration Insecure Direct Object Reference

On N-central, it is possible for any authenticated user to read, write and modify syslog configuration across customers on an N-central server. This vulnerability is present in all deployments of N-central prior to 2025.2.

Published Updated Sources: cvelistV5, N-able

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

n able

n_central

CVSS base

8.3

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

n able

Products (1)

n central

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.3CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-284

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1027.009Obfuscated Files or Information: Embedded Payloads
  • T1546.004Event Triggered Execution: .bash_profile and .bashrc
  • T1546.016Event Triggered Execution: Installer Packages

References

1 on the record

Elsewhere on this site

  • n ableevery CVE for this vendor
  • CWE-284other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.