dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-13249

MEDIUM · 6.3 CVSS v3.1 Published 2025-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A security vulnerability has been detected in Jiusi OA up to 20251102. This affects an unknown function of the file /OfficeServer?isAjaxDownloadTemplate=false of the component OfficeServer Interface. Such manipulation of the argument FileData leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.

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 confidence

Jiusi OA contains an unrestricted file upload vulnerability in the OfficeServer interface. Attackers can exploit the /OfficeServer endpoint by manipulating the FileData parameter to upload arbitrary files to the server, potentially leading to remote code execution if uploaded files are stored in a web-accessible executable directory.

MitigationImplement strict server-side file type validation with allowlist approach, store uploaded files outside the web root in non-executable directories, and apply proper authentication/authorization controls to the OfficeServer endpoint. If available, apply vendor patch for versions beyond 20251102.

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
Low
Integrity
Low
Availability
Low

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

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. Identify Jiusi OA installation
    Check for Jiusi OA by reviewing running web services, installed applications, or common installation directories. Look for the service name 'Jiusi' or 'OA' in running processes or installed programs.
    Affected if Jiusi OA is installed and running on the system
  2. Locate the OfficeServer endpoint
    Review web server configuration files (such as IIS web.config, Apache/nginx configs, or embedded server configs) to identify if the /OfficeServer route is mapped and accessible.
    Affected if The /OfficeServer endpoint exists and is routable in the web application
  3. Verify file upload capability on OfficeServer
    Review the application's configuration or source code related to the OfficeServer component. Check for file upload handling logic in OfficeServer.aspx, OfficeServer.jsp, or corresponding server-side files.
    Affected if FileData or similar file upload parameter is accepted by the OfficeServer endpoint without proper validation
  4. Check uploaded file storage location
    Examine the web server configuration and application file storage paths to determine where uploaded files are saved. Look for upload directories within the web root (such as /upload, /files, /attachments) versus directories outside the web accessible path.
    Affected if Uploaded files are stored in web-accessible directories that can execute code (such as .asp, .jsp, .php, .exe locations)
  5. Compare installed version to known fixed release
    If a version number is visible in the application (about page, footer, or config files), compare it against the patched version 20251102. Versions earlier than or equal to 20251102 are likely vulnerable.
    Affected if Installed version is 20251102 or earlier, or version information is unavailable (treat as potentially affected)

A user is affected if Jiusi OA is installed with the /OfficeServer endpoint accessible and accepting unrestricted file uploads to a web-accessible directory, particularly on versions 20251102 or earlier.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict server-side file type validation with allowlist approach, store uploaded files outside the web root in non-executable directories, and apply proper authentication/authorization controls to the OfficeServer endpoint. If available, apply vendor patch for versions beyond 20251102.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13249 — 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-13249 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