CVE-2025-0708
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 · uneditedA vulnerability was found in fumiao opencms 2.2. It has been declared as problematic. This vulnerability affects unknown code of the file /admin/model/addOrUpdate of the component Add Model Management Page. The manipulation of the argument 模板前缀 leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in fumiao opencms 2.2 within the Add Model Management Page (/admin/model/addOrUpdate). The '模板前缀' (template prefix) parameter accepts unsanitized user input that is later rendered without proper output encoding, allowing execution of arbitrary JavaScript in the context of other users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Fumiao Opencms versionAccess the administration interface and navigate to the system information or about page, or check the application's footer/version display. Alternatively, inspect the HTTP headers or the application's metadata files if accessible.Affected if The installed version is exactly 2.2 (Fumiao Opencms = 2.2)
-
Confirm access to Model ManagementLog into the admin panel and attempt to navigate to /admin/model/addOrUpdate or find the 'Add Model' or 'Model Management' section in the navigation menu.Affected if You have administrative access to reach the vulnerable endpoint /admin/model/addOrUpdate
-
Locate the template prefix parameterIn the Add Model Management Page (/admin/model/addOrUpdate), identify the input field labeled '模板前缀' (template prefix).Affected if The '模板前缀' input field exists and accepts user input on the page
-
Inspect stored output renderingSubmit a benign test string (such as a simple alphanumeric value) in the '模板前缀' field, save the model, then view or preview the model to see if your input is reflected in the rendered output without visible encoding (compare how special characters like < > " appear).Affected if The submitted '模板前缀' value is rendered back in HTML output without encoding (raw < and > characters appear as expected, indicating no sanitization is applied)
You are affected if you are running Fumiao Opencms version 2.2 and have access to the Model Management feature where the '模板前缀' parameter can be submitted and subsequently rendered without output encoding.
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 dataImplement server-side input validation and context-aware output encoding for the '模板前缀' parameter. Additionally, deploy a Content Security Policy (CSP) header to mitigate XSS execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0708 — 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-0708 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