dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-2407

CRITICAL · 9.3 CVSS v4.0 Published 2025-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authentication & Authorization in Web-API in Mobatime AMX MTAPI v6 on IIS allows adversaries to unrestricted access via the network. The vulnerability is fixed in Version 1.5.

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 · high confidence

Missing authentication and authorization in the Web-API component of Mobatime AMX MTAPI v6 running on IIS enables unauthenticated remote attackers to gain unrestricted access to the API over the network.

MitigationUpgrade Mobatime AMX MTAPI to Version 1.5 which contains the fix for this vulnerability.

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
None
Authentication
Y
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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:Y/R:U/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Mobatime AMX MTAPI is installed
    Check for Mobatime AMX MTAPI installation directories (commonly under C:\Program Files\ or C:\Program Files (x86)\ on Windows servers), or look for MTAPI in IIS via IIS Manager under Sites or Application Pools.
    Affected if The product is present on the server.
  2. Confirm the installed MTAPI version
    Locate the MTAPI installation folder and check version.dll, version.txt, or the application binary metadata. Alternatively, access the API endpoint and inspect HTTP response headers or documentation files for version strings.
    Affected if The installed version is MTAPI v6 (or any version prior to 1.5).
  3. Identify if Web-API component is configured
    In IIS Manager, expand the MTAPI site and look for an application or virtual directory exposing the /api or /mtapi endpoints. Check web.config files in the MTAPI folder for API-related route configurations.
    Affected if The Web-API component is exposed and accessible via HTTP.
  4. Verify the server is running on IIS
    Confirm IIS is the web server hosting MTAPI: open IIS Manager, run 'appcmd list site' from an elevated command prompt, or check that MTAPI worker processes (w3wp.exe) are running under the IIS worker pool account.
    Affected if MTAPI is hosted on IIS (as stated in the affected product description).
  5. Test for unauthenticated API access
    Send an HTTP request to the MTAPI Web-API endpoint (such as GET http://<server>/api/ or the specific MTAPI endpoint) without providing any authentication credentials (no Authorization header, no API key, no session cookie). Observe whether the request succeeds and returns data.
    Affected if The API responds with successful data or valid JSON without requiring any authentication.

A user is affected if Mobatime AMX MTAPI v6 is installed on IIS with the Web-API component exposed and the endpoint accepts unauthenticated requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mobatime AMX MTAPI to Version 1.5 which contains the fix for this vulnerability.

Recommended fix Moderate confidence

Mobatime AMX MTAPI v6 to Version 1.5

  1. 1. Identify the current version of Mobatime AMX MTAPI v6 running on the IIS server
  2. 2. Download Mobatime AMX MTAPI version 1.5 or later from the official vendor source
  3. 3. Backup the current MTAPI installation and configuration files
  4. 4. Stop the IIS web server or the MTAPI application pool
  5. 5. Install version 1.5 of Mobatime AMX MTAPI
  6. 6. Restore the configuration files from the backup
  7. 7. Start the IIS web server and verify the application is running
  8. 8. Test that authentication is now required for Web-API access

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2407 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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