CVE-2025-13319
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn injection vulnerability has been discovered in the API feature in Digi On-Prem Manager, enabling an attacker with valid API tokens to inject SQL via crafted input. The API is not enabled by default, and a valid API token is required to perform the attack.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the API feature of Digi On-Prem Manager allows authenticated attackers with valid API tokens to inject arbitrary SQL commands via crafted input fields. The API must be explicitly enabled for exploitation, reducing the default attack surface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Digi On-Prem Manager is installedLocate the installation directory or check for the application process/service running on the system. Common locations may include /opt/digi, C:\Program Files\Digi, or a dedicated application server directory.Affected if The software is not present on the system, the vulnerability does not apply.
-
Check if API feature is enabledExamine the configuration files (typically config.xml, settings.conf, or similar) in the application directory for an API enable flag, or look for API-related settings in the web management interface.Affected if API is disabled - the vulnerability cannot be exploited as the attack surface is not exposed.
-
Review API configuration for authentication settingsInspect the API configuration to confirm whether API token-based authentication is configured and active. Look for token generation or API key settings.Affected if API tokens are not configured or the API requires no authentication - exploitation requires valid API tokens per the CVE description.
-
Check application version against known releasesIf version information is accessible (about page, version file, or application metadata), compare the installed version to any available release notes or changelogs for Digi On-Prem Manager.Affected if Version cannot be determined or is not within the affected range - the specific vulnerability may not apply.
-
Review API access logs for anomalous queriesExamine API request logs, audit logs, or web server logs for unusual SQL-like patterns, unexpected input, or suspicious API calls that may indicate exploitation attempts.Affected if Evidence of SQL injection attempts in logs suggests potential exploitation of this vulnerability.
A user is affected if Digi On-Prem Manager is installed, the API feature is explicitly enabled, and API token authentication is configured - allowing authenticated attackers to inject SQL commands through API input fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable the API feature if not required; if needed, implement strict input validation and use parameterized queries to prevent SQL injection, and rotate any potentially compromised API tokens.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13319 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data