CVE-2024-7873: Stored XSS in Veribilim Software's Veribase Order Management
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting'), Improper Encoding or Escaping of Output, CWE - 83 Improper Neutralization of Script in Attributes in a Web Page vulnerability in Veribilim Software Veribase Order allows Stored XSS, Cross-Site Scripting (XSS), Exploit Script-Based APIs, XSS Through HTTP Headers.
This issue affects Veribase Order: before v4.010.3.
Security readout for executives and security teams
Plain-English summary
Veribase Order before v4.010.3 has a stored cross-site scripting flaw. Malicious content can be saved in the application and later run in another user’s browser when viewed. For business leaders, the concern is unauthorized actions, data exposure, and loss of trust in an order management workflow.
Executive priority
Treat this as urgent for any active Veribase Order deployment. The score is critical and the issue can affect confidentiality, integrity, and availability through user browsers, but available sources do not prove active exploitation.
Technical view
The CVE describes improper input neutralization and output encoding in Veribilim Software Veribase Order. It is categorized as stored XSS with script execution through generated pages, attributes, headers, and script-based APIs. The CVSS v4.0 score is 9.4, with network attack vector, low complexity, no privileges required, and user interaction required.
Likely exposure
Exposure is limited to organizations running Veribilim Software Veribase Order versions before v4.010.3. Risk is higher where the application accepts untrusted order or header-related data and where administrators or staff view stored records through a browser.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates an unauthenticated network attacker can plant content, but successful impact requires a user to view affected content. No exploit code or campaign evidence is cited.
Researcher notes
Evidence is strongest for product, vulnerability class, severity, and affected version boundary. It is weaker on precise vulnerable fields, exploit maturity, and vendor-side mitigation details. One listed USOM URL is marked broken in the bundle, so rely on reachable CVE and government sources.
Mitigation direction
Confirm the deployed Veribase Order version with the application owner.
Upgrade to v4.010.3 or later if vendor guidance confirms remediation.
Review Veribilim and Turkish government advisories for official instructions.
Restrict application access until remediation is complete where feasible.
Monitor for suspicious stored content and unusual user-session activity.
Validation and detection
Inventory all Veribase Order deployments and record exact versions.
Check whether any instance is older than v4.010.3.
Review application logs for unexpected script-like input or suspicious headers.
Verify output encoding controls after applying the vendor-supported update.
Confirm no exposed public route unnecessarily reaches the order management interface.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-116: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-116 · source CWE mapping
Improper Encoding or Escaping of Output
Improper Encoding or Escaping of Output represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.