Skip to content
Noroxi
NVD / CVE Program· CNA SEC-VLab

CVE-2025-9943: Unauthenticated SQL Injection Vulnerability in Shibboleth Service Provider

Noroxi assessment

Priority: Monitor (action score 36/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.41% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: shibboleth-sp (Debian:11) 3.2.2+dfsg1-1+deb11u1; shibboleth-sp (Debian:12) 3.4.1+dfsg-2+deb12u1; shibboleth-sp (Debian:13) 3.5.0+dfsg-2+deb13u1.

Low priority for now. Upgrade to shibboleth-sp (Debian:11) 3.2.2+dfsg1-1+deb11u1; shibboleth-sp (Debian:12) 3.4.1+dfsg-2+deb12u1; shibboleth-sp (Debian:13) 3.5.0+dfsg-2+deb13u1 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

An SQL injection vulnerability has been identified in the "ID" attribute of the SAML response when the replay cache of the Shibboleth Service Provider (SP) is configured to use an SQL database as storage service. An unauthenticated attacker can exploit this issue via blind SQL injection, allowing for the extraction of arbitrary data from the database, if the database connection is configured to use the ODBC plugin. The vulnerability arises from insufficient escaping of single quotes in the class SQLString (file odbc-store.cpp, lines 253-271). This issue affects Shibboleth Service Provider through 3.5.0.

CriticalCVSS 9.1 · v3.1—No exploit Fix available
Published
Sep 10, 2025
Updated
Sep 25, 2026
EPSS
0.4% · 35th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2025-9943

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

—

Versions reported by the vendor

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

  • Shibboleth Service Provider

    • up to and including 3.5.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11shibboleth-spbefore 3.2.2+dfsg1-1+deb11u13.2.2+dfsg1-1+deb11u1
Debian:12shibboleth-spbefore 3.4.1+dfsg-2+deb12u13.4.1+dfsg-2+deb12u1
Debian:13shibboleth-spbefore 3.5.0+dfsg-2+deb13u13.5.0+dfsg-2+deb13u1
Debian:14shibboleth-spbefore 3.5.1+dfsg-13.5.1+dfsg-1
openSUSE:Leap 16.0shibboleth-spbefore 3.5.0-160000.3.13.5.0-160000.3.1
openSUSE:Tumbleweedshibboleth-spbefore 3.5.1-1.13.5.1-1.1
SUSE:Linux Enterprise Module for Server Applications 15 SP7shibboleth-spbefore 3.1.0-150300.3.6.13.1.0-150300.3.6.1
SUSE:Linux Enterprise Server 12 SP5-LTSSshibboleth-spbefore 2.5.5-6.9.12.5.5-6.9.1
SUSE:Linux Enterprise Server 16.0shibboleth-spbefore 3.5.0-160000.3.13.5.0-160000.3.1

Other highest-scoring records for the same primary product.

  • CVE-2017-16852shibsp/metadata/DynamicMetadataProvider.cpp in the Dynamic MetadataProvider plugin in Shibboleth Service Provider before 2.6.1 fails to prop
    32Monitor
  • CVE-2021-31826Shibboleth Service Provider 3.x before 3.2.2 is prone to a NULL pointer dereference flaw involving the session recovery feature.
    31Monitor
  • CVE-2019-19191Shibboleth Service Provider (SP) 3.x before 3.1.0 shipped a spec file that calls chown on files in a directory controlled by the service use
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2010-2450Nov 7, 2019 · The keygen.sh script in Shibboleth SP 2.0 (located in /usr/local/etc/shibboleth by default) uses OpenSSL to create a DES private key which i
    30Monitor
  • ← EarlierCVE-2021-28963Mar 22, 2021 · Shibboleth Service Provider before 3.2.1 allows content injection because template generation uses attacker-controlled parameters.
    21Monitor
  • ← EarlierCVE-2023-22947Jan 10, 2023 · Insecure folder permissions in the Windows installation path of Shibboleth Service Provider (SP) before 3.4.1 allow an unprivileged local at
    29Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
debian:shibboleth-sp3.4.1+dfsg-2+deb12u1 · Debian:12Package registry (OSV)
opensuse:shibboleth-sp3.5.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:shibboleth-sp3.5.0-160000.3.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

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

Variant candidates

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

No nightly-computed relations.

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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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.

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

Vulnerable

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

Fixed

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

Change log

  1. Fix✗ → ✓

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

References

All records