dbcve.org
OpinioApplication · Objectplanet

CVE-2025-13873

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Stored Cross-Site Scripting (XSS) in the survey-import feature of ObjectPlanet Opinio 7.26 rev12562 on web application allows an attacker to inject arbitrary JavaScript code, which executes in the browsing context of any visitor accessing the compromised survey.

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

Stored Cross-Site Scripting (XSS) vulnerability in the survey-import feature of ObjectPlanet Opinio 7.26 allows attackers to inject malicious JavaScript through imported survey data. When other users access the compromised survey, the injected script executes in their browser context, potentially enabling session hijacking, credential theft, or defacement.

MitigationImplement strict input validation and output encoding/sanitization on all survey data during the import process. The fix should neutralize script tags and event handlers in user-supplied content before storage and before rendering.

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
OpinioApplication
Affected:= 7.26

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
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 checks

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

  1. Verify ObjectPlanet Opinio version
    Locate and inspect the installed Opinio version number using your system's software inventory, about page, or admin panel. Common locations include the application header, help menu, or version manifest file.
    Affected if The installed version is exactly 7.26
  2. Confirm survey-import feature access
    Check whether the survey-import functionality is available and accessible in the Opinio admin interface or API endpoints.
    Affected if The survey-import feature is enabled and accessible to users
  3. Identify imported surveys in the system
    Review the survey database or file storage for surveys created through the import function. Query for surveys with import timestamps or examine survey metadata.
    Affected if Any surveys exist that were created via the import feature
  4. Inspect imported survey content for malicious payloads
    Examine the raw data fields of imported surveys, including question text, answer options, and metadata. Look for unencoded script tags, event handlers (onclick, onload, etc.), or suspicious JavaScript references.
    Affected if Imported survey data contains raw script tags, event handlers, or unescaped JavaScript in display fields
  5. Verify output encoding is absent on survey rendering
    Test viewing an imported survey as a regular user would. Submit a test survey with typical content and inspect the page source to see if content is rendered with proper HTML encoding.
    Affected if Survey content renders without HTML entity encoding (e.g., <script> appears as literal <script> in the page source)

A system is affected if it runs ObjectPlanet Opinio version 7.26, has the survey-import feature enabled, and contains surveys imported from untrusted sources that render without proper output encoding.

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 input validation and output encoding/sanitization on all survey data during the import process. The fix should neutralize script tags and event handlers in user-supplied content before storage and before rendering.

Fix this in Opinio Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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