Book Store Management System v1.0 was discovered to contain a cross-site scripting (XSS) vulnerability in /bsms_ci/index.php/book. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the writer parameter.

50 XSS vulnerabilities.

Different sources that saved in the database in this project.

// In file application/models/M\_book.php
$object\=array(
      'book\_title'\=>$this\->input\->post('book\_title'),
      'year'\=>$this\->input\->post('year'),
      'price'\=>$this\->input\->post('price'),
      'category\_code'\=>$this\->input\->post('category'),
      'publisher'\=>$this\->input\->post('publisher'),
      'writer'\=>$this\->input\->post('writer'),
      'stock'\=>$this\->input\->post('stock')
    );
return $this\->db\->insert('book', $object);

// In file application/models/M\_transaction.php
$object\=array(
    'user\_code'\=>$this\->input\->post('user\_code'),
    'buyer\_name'\=>$this\->input\->post('buyer\_name'),
    'tgl' => date('Y-m-d'),
    'total'\=>$this\->input\->post('total'),
    'bookname'\=>$this\->input\->post('bookname'),
    'book\_qty'\=>$this\->input\->post('book\_qty'),
  );
$this\->db\->insert('transaction', $object);

These sources will pass from the database to the view files.

// In file application/views/v\_book.php
<td><?=$book\->book\_title?></td\>
<td\><?=$book\->year?></td\>
<td\><?=$book\->category\_name?></td\>
<td\><?=$book\->publisher?></td\>
<td\><?=$book\->writer?></td\>
<td\><?=$book\->stock?></td\>

// In file application/views/v\_transaction.php
<td\><?=$book\->book\_title?></td\>
<td\><?=$book\->category\_name?></td\>
<td class\="text-right"\>$<?=$book\->price?></td\>
<td class\="text-right"\><?=$book\->stock?></td\>
                                                      
<?php foreach ($transaction as $transaction): ?>
<option class\="text-dark" value\="<?=$transaction\->user\_code?>"\><?=$transaction\->fullname?></option\>
<?php endforeach ?>

CVE-2023-23024: XSS in Book Store

Cross Site Scripting (XSS) vulnerability in Kalkun 0.8.0 via username input in file User_model.php.

Link: https://github.com/kalkun-sms/Kalkun

XSS vulnerability with the user name.

We see that the username will be setted in the DB without sanitization in file Kalkun-devel\\application\\models\\User\_model.php

$this\->db\->set('username', trim($this\->input\->post('username')));

Then the username retrieved from the DB and set in the session then redirect to 'kalkun' in file Kalkun-devel\\application\\models\\Kalkun\_model.php

function login(){
  $username = $this\->input\->post('username');
  $this\->db\->from('user');
  $this\->db\->where('username', $username);
  $query = $this\->db\->get();
  
  if ($query\->num\_rows() === 1 && password\_verify($this\->input\->post('password'), $query\->row('password')))
  {
	  //..
	  $this\->session\->set\_userdata('username', $query\->row('username'));
         //...
  }
  if ($this\->input\->post('r\_url'))
  {
  redirect($this\->input\->post('r\_url'));
  }
  else
  {
  redirect('kalkun');
  }
}

In file Kalkun-devel\\application\\controllers\\Kalkun.php

function index()
{
  //...
  $this\->load\->view('main/layout', $data);
}

In file Kalkun-devel\\application\\views\\main\\layout.php

<?php $this\->load\->view('main/dock');?>

Finally, in file Kalkun-devel\\application\\views\\main\\dock.php

<?php echo $this\->session\->userdata('username');?>

CVE-2023-23015: XSS Kalkun

Cross Site Scripting (XSS) vulnerability in InventorySystem thru commit e08fbbe17902146313501ed0b5feba81d58f455c (on Apr 23, 2021) via edit_store_name and edit_active inputs in file InventorySystem.php.

Hello,

I would like to report for possible XSS vulnerabilities.

For example,

In file InventorySystem-master\\application\\controllers\\Stores.php in update function

$data = array(
	'name' => $this\->input\->post('edit\_store\_name'),
	'active' => $this\->input\->post('edit\_active'),	
);

$update = $this\->model\_stores\->update($data, $id);

In file InventorySystem-master\\application\\models\\Model\_stores.php

public function update($data, $id){
  if($data && $id) {
	  $this\->db\->where('id', $id);
	  $update = $this\->db\->update('stores', $data);
	  return ($update == true) ? true : false;
  }
}

Then In file InventorySystem-master\\application\\controllers\\Stores.php

public function fetchStoresDataById($id) {
  if($id) {
	  $data = $this\->model\_stores\->getStoresData($id);
	  echo json\_encode($data);
  }
}

In file InventorySystem-master\\application\\models\\Model\_stores.php

public function getStoresData($id = null){
  if($id) {
	  $sql = "SELECT \* FROM \`stores\` where id = ?";
	  $query = $this\->db\->query($sql, array($id));
	  return $query\->row\_array();
  }
  
  $sql = "SELECT \* FROM \`stores\`";
  $query = $this\->db\->query($sql);
  return $query\->result\_array();
}

CVE-2023-23014: Possible XSS vulnerabilities · Issue #23 · ronknight/InventorySystem

Cross Site Scripting (XSS) vulnerability in craigrodway classroombookings 2.6.4 allows attackers to execute arbitrary code or other unspecified impacts via the input bgcol in file Weeks.php.

Link: https://github.com/craigrodway/classroombookings

XSS vulnerability.

In file classroombookings-master\\application\\controllers\\Weeks.php in function save\_week

the input 'bgcol' will be saved in the DB and passed to the view when it will be printed without sanitization.

$data = array(
	'name' => $this\->input\->post('name'),
	'bgcol' => $this\->input\->post('bgcol'),
);
if ($week\_id = $this\->weeks\_model\->insert($data)) {
//...
}

In file classroombookings-master\\application\\models\\Weeks\_model.php

public function insert($data){
  $data = $this\->sleep\_values($data);
  
  $insert = $this\->db\->insert($this\->table, $data);
  
  return $insert ? $this\->db\->insert\_id() : FALSE;
}

In file classroombookings-master\\application\\controllers\\Weeks.php in function save\_week

public function index(){
  $this\->data\['weeks'\] = $this\->weeks\_model\->get\_all();
  $this\->data\['title'\] = $this\->data\['showtitle'\] = 'Timetable Weeks';
  
  $body = $this\->load\->view('weeks/index', $this\->data, TRUE);
  
  $this\->data\['body'\] = $body;
  
  return $this\->render();
}

In file classroombookings-master\\application\\models\\Weeks\_model.php

public function get\_all(){
  $query = $this\->db\->from($this\->table)
	  ->order\_by('name', 'ASC')
	  ->get();
  
  if ($query\->num\_rows() > 0) {
	  $result = $query\->result();
	  //..
	  return $result;
  }
}

The In file C:\\transfer\_projects\\classroombooking\\classroombookings-master\\application\\views\\weeks\\index.php

<?php
foreach ($weeks as $week) {
//...
	$dot = week\_dot($week);
  echo "<td style='text-align:center'>{$dot}</td>";
//...
}
?>

In file classroombookings-master\\application\\helpers\\week\_helper.php

function week\_dot($week, $size = 'md')
{
	$col = $week\->bgcol;
	$col = str\_replace('#', '', $col);
	$col = '#' . $col;

	$out = "<span class='dot dot-week dot-size-{$size}' style='background-color:{$col}'></span>";
	return $out;
}

CVE-2023-23012: XSS in classroombookings

Cross Site Scripting (XSS) vulnerability in Ecommerce-CodeIgniter-Bootstrap thru commit d5904379ca55014c5df34c67deda982c73dc7fe5 (on Dec 27, 2022), allows attackers to execute arbitrary code via the languages and trans_load parameters in file add_product.php.

@@ -18,37 +18,37 @@ <div class\="form-group available-translations"\> <b\>Languages</b\> <?php foreach ($languages as $language) { ?> <button type\="button" data-locale-change\="<?= $language\->abbr ?>" class\="btn btn-default locale-change text-uppercase <?= $language\->abbr == MY\_DEFAULT\_LANGUAGE\_ABBR ? 'active' : '' ?>"\> <img src\="<?= base\_url('attachments/lang\_flags/' . $language\->flag) ?>" alt\=""\> <?= $language\->abbr ?> <button type\="button" data-locale-change\="<?= htmlspecialchars($language\->abbr) ?>" class\="btn btn-default locale-change text-uppercase <?= $language\->abbr == MY\_DEFAULT\_LANGUAGE\_ABBR ? 'active' : '' ?>"\> <img src\="<?= base\_url('attachments/lang\_flags/' . htmlspecialchars($language\->flag)) ?>" alt\=""\> <?= htmlspecialchars($language\->abbr) ?> </button\> <?php } ?> </div\> <?php $i = 0; foreach ($languages as $language) { ?> <div class\="locale-container locale-container-<?= $language\->abbr ?>" <?= $language\->abbr == MY\_DEFAULT\_LANGUAGE\_ABBR ? 'style="display:block;"' : '' ?>\> <input type\="hidden" name\="translations\[\]" value\="<?= $language\->abbr ?>"\> <div class\="locale-container locale-container-<?= htmlspecialchars($language\->abbr) ?>" <?= $language\->abbr == MY\_DEFAULT\_LANGUAGE\_ABBR ? 'style="display:block;"' : '' ?>\> <input type\="hidden" name\="translations\[\]" value\="<?= htmlspecialchars($language\->abbr) ?>"\> <div class\="form-group"\> <img src\="<?= base\_url('attachments/lang\_flags/' . $language\->flag) ?>" alt\="<?= $language\->name ?>" class\="language"\> <input type\="text" name\="title\[\]" placeholder\="<?= lang('vendor\_product\_name') ?>" value\="<?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['title'\]) ? $trans\_load\[$language\->abbr\]\['title'\] : '' ?>" class\="form-control"\> <img src\="<?= base\_url('attachments/lang\_flags/' . htmlspecialchars($language\->flag)) ?>" alt\="<?= htmlspecialchars($language\->name) ?>" class\="language"\> <input type\="text" name\="title\[\]" placeholder\="<?= lang('vendor\_product\_name') ?>" value\="<?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['title'\]) ? htmlentities($trans\_load\[$language\->abbr\]\['title'\], ENT\_QUOTES, 'UTF-8') : '' ?>" class\="form-control"\> </div\> <label\><?= lang('vendor\_product\_description') ?> <img src\="<?= base\_url('attachments/lang\_flags/' . $language\->flag) ?>" alt\="<?= $language\->name ?>"\></label\> <label\><?= lang('vendor\_product\_description') ?> <img src\="<?= base\_url('attachments/lang\_flags/' . htmlspecialchars($language\->flag)) ?>" alt\="<?= htmlspecialchars($language\->name) ?>"\></label\> <div class\="form-group"\> <textarea class\="form-control" name\="description\[\]" id\="description<?= $i ?>"\><?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['description'\]) ? $trans\_load\[$language\->abbr\]\['description'\] : '' ?></textarea\> <textarea class\="form-control" name\="description\[\]" id\="description<?= $i ?>"\><?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['description'\]) ? htmlentities($trans\_load\[$language\->abbr\]\['description'\], ENT\_QUOTES, 'UTF-8') : '' ?></textarea\> </div\> <script\> CKEDITOR.replace('description<?= $i ?>'); CKEDITOR.config.entities \= false; </script\> <div class\="form-group"\> <img src\="<?= base\_url('attachments/lang\_flags/' . $language\->flag) ?>" alt\="" class\="language"\> <input type\="text" name\="price\[\]" value\="<?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['price'\]) ? $trans\_load\[$language\->abbr\]\['price'\] : '' ?>" placeholder\="<?= lang('vendor\_price') ?>" class\="form-control"\> <img src\="<?= base\_url('attachments/lang\_flags/' . htmlspecialchars($language\->flag)) ?>" alt\="" class\="language"\> <input type\="text" name\="price\[\]" value\="<?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['price'\]) ? htmlentities($trans\_load\[$language\->abbr\]\['price'\], ENT\_QUOTES, 'UTF-8') : '' ?>" placeholder\="<?= lang('vendor\_price') ?>" class\="form-control"\> </div\> <div class\="form-group"\> <img src\="<?= base\_url('attachments/lang\_flags/' . $language\->flag) ?>" alt\="" class\="language"\> <input type\="text" name\="old\_price\[\]" value\="<?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['old\_price'\]) ? $trans\_load\[$language\->abbr\]\['old\_price'\] : '' ?>" placeholder\="<?= lang('vendor\_old\_price') ?>" class\="form-control"\> <img src\="<?= base\_url('attachments/lang\_flags/' . htmlspecialchars($language\->flag)) ?>" alt\="" class\="language"\> <input type\="text" name\="old\_price\[\]" value\="<?= $trans\_load != null && isset($trans\_load\[$language\->abbr\]\['old\_price'\]) ? htmlentities($trans\_load\[$language\->abbr\]\['old\_price'\], ENT\_QUOTES, 'UTF-8') : '' ?>" placeholder\="<?= lang('vendor\_old\_price') ?>" class\="form-control"\> </div\> </div\> <?php

CVE-2023-23010: xss fixes · kirilkirkov/Ecommerce-CodeIgniter-Bootstrap@d590437

In DPA 2022.4 and older releases, generated heap memory dumps contain sensitive information in cleartext.

Release date: January 18, 2023

These release notes describe the new features, improvements, and fixed issues in Database Performance Analyzer 2023.1. They also provide information about upgrades and describe workarounds for known issues.

**Learn more**

*   For information on the latest hotfixes, see DPA hotfixes.
*   For release notes for previous DPA versions, see Previous Version documentation.
*   For information about requirements, see DPA system requirements.
*   For information about working with DPA, see the DPA Administrator Guide.

**New features and improvements in DPA**

Return to top

DPA 2023.1 offers new features and improvements compared to previous releases of DPA.

**Improvements to importing alerts, rules, and custom properties**

DPA 2022.4 introduced the ability to export the alerts, rules, and custom properties that are configured on one DPA server and import them to another server. DPA 2023.1 improves the import functionality in the following ways:

*   You can specify which entities to import. The import wizard displays a list of the alerts, rules, and custom properties to be imported. Clear the checkbox next to any entity you don't want to import.
    
*   You can choose to overwrite existing entities with the same name. If you overwrite an entity, the existing entity is replaced by the imported entity.
    

**Additions to systems requirements and monitored instances**

 

Category

Vender and version

Repository database

Microsoft SQL Server 2022, Windows or Linux

Monitored database instances

Microsoft SQL Server 2022, Windows or Linux

VMware

VMware vCenter Server 7.0

VMware ESX/ESXi Host 7.0

For more information, see the DPA 2023.1 system requirements and Database instances DPA can monitor.

**Fixed issues in DPA 2023.1**

Return to top

DPA 2023.1 fixes the following issues.

 

Case number

Description

01144021, 01233510, 01234275

In deployments with an Oracle repository that monitor Oracle database instances, index analysis runs successfully. Logs no longer include the error message Unable to run index analysis.

01080326, 01129290, 01234534, 01236488

Files in the /tomcat/logs/ directory, such as catalina.out, stderr.log, and catalina._YYYY-MM-DD_.log, no longer grow quickly and consume a large amount of space.

00978208, 01076887

Collecting a large number of metrics (for example, because you have configured many custom metrics), can sometimes cause DPA monitoring to stop periodically. DPA 2023.1 includes metrics setting in the system.properties files that can be adjusted to avoid this issue. For information on adjusting these properties, see Scale DPA for the number of databases being monitored and the number of custom metrics.

00560405, 00850966, 01061361, 01128672

In previous versions, when DPA was installed on Windows the installer ran a VBS script to create the Windows service. If an organization had a security policy that prevented VBS scripts from running, the service was not created and DPA would not start. To prevent this issue, DPA 2023.1 runs a Powershell script instead of a VBS script.

**SolarWinds CVEs**

SolarWinds would like to thank our Security Researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.

   

CVE-ID

Vulnerability Title

Description

Severity

CVE-2022-38110

Reflected Cross-Site Scripting Vulnerability

In DPA 2022.4 and older releases, certain URL vectors are susceptible to authenticated reflected cross-site scripting.

6.3 Medium

CVE-2022-38112

Sensitive Information Disclosure Vulnerability

In DPA 2022.4 and older releases, generated heap memory dumps contain sensitive information in cleartext.

6.3 Medium

**Notes - BugCrowd**

SolarWinds would like to additionally thank our Bugcrowd community for their continued help in testing our products and keeping them secure

**New customer installation**

Return to top

For information about installing DPA, see the DPA Installation and Upgrade Guide. You can download a free trial from the SolarWinds website.

**Before you upgrade!**

If you are upgrading from DPA 2022.3 and you configured that version for SAML authentication, be aware that 2022.4 and later versions include changes to the SAML configuration. After the upgrade, no one will be able to log in with SAML until you update the configuration.

*   **Before** you upgrade, make sure you have a local login available.
    
*   **After** the upgrade, log in as a local user and complete the steps under SAML configuration changes in the DPA 2022.3 release notes to update the SAML configuration.
    

**How to upgrade**

If you are upgrading from an earlier version, use the following resources to plan and implement your upgrade:

*   Use the DPA Installation and Upgrade Guide to help you plan and execute your upgrade.
*   When you are ready, download the upgrade package from the SolarWinds Customer Portal.

**Known issues**

Return to top

 

Importing an alert definition without the associated database assignment rule

**Issue**

In some situations, the log file shows the status of an imported alert definition as both Imported and Failed. This occurs when the alert definition uses a database assignment rule, but the rule was not imported and did not already exist on the server.

The two statuses indicate that the alert definition was imported but the attempt to associate the database assignment rule failed.

**Resolution or Workaround**

When you import an alert definition that uses a database assignment rule, either import the rule or ensure that it already exists on the server.

If you imported an alert definition and the associated rule is missing, you must edit the alert definition to specify the database instances. (You can specify instances by manually selecting them or by applying a rule.)

 

REST API does not work when you access DPA with SAML login credentials

**Issue**

If you access DPA with SAML login credentials and you generate a refresh token, the following message is displayed when you attempt to use that refresh token to access the REST API:

You are not authorized to perform this action. Contact your DPA administrator.

**Resolution or Workaround**

Access DPA with a local login when you generate the refresh token.

 

The database name is not updated for stored procedures

**Issue**

If a stored procedure name includes the name of a database and it is copied to a different database, the database name is not updated. When DPA shows information about the copied stored procedure, the hash is the same as the first and the information appears to be incorrect.

**Resolution or Workaround**

If you experience this issue, complete the following steps:

1.  Run the following command against the DPA repository database (replacing <HashValue> with the stored procedure's hash value):
    
    delete from ignite.CONST_<DBID> where H = '<HashValue>'
    
2.  Restart DPA.

 

Registering an Azure SQL database instance fails when the privileged user is an Azure AD user

**Issue**

When registering an Azure SQL database, if you let DPA create the monitoring user and select an Azure Active Directory (AD) user as the privileged user, registration fails on the last step with the message Connection test to database as monitoring user failed.

**Resolution or Workaround**

Select the option 'I'll create the contained user or login', and follow the instructions to create the monitoring user manually.

 

Adding a distributed AG to a server prevents DPA from monitoring non-distributed AGs on the server

**Issue**

If DPA is monitoring non-distributed SQL Server Availability Groups (AGs) on a server and you add a distributed AG to the server, DPA stops monitoring the non-distributed AGs.

**Resolution or Workaround**

Do not add a distributed AG to the server.

 

Microsoft reports incorrect metric values for SQL Server on Linux

**Issue**

When you monitor a **SQL Server 2017** database instance that runs on a Linux server:

*   The O/S CPU Utilization resource always shows usage at 100%.
*   The Instance CPU Utilization resource always shows usage at 100%.
*   The O/S Memory Utilization resource always shows usage at 0%.

When you monitor a **SQL Server 2019** database instance that runs on a Linux server:

*   The O/S CPU Utilization resource always shows usage at 100%.
*   In some cases, the Instance CPU Utilization resource always shows usage at 100%.

Microsoft reports these values.

**Resolution or Workaround**

Disregard the values that are incorrect on your version of SQL Server. You can also disable the collection of a metric that shows incorrect data.

 

DPA fails to reconnect after losing its connection to a SQL Server instance

**Issue**

When DPA loses its connection to a monitored SQL Server instance (for example, when the DPA server is rebooted), and Windows authentication is used, DPA is sometimes unable to reconnect to the instance. This can happen if DPA attempts to connect before SQL Server has been able to connect to Active Directory. DPA interprets the rejected connection attempt as possibly occuring because the credentials were incorrect. To avoid being locked out of the account, DPA does not keep trying to reconnect. Messages such as the following appear in the logs:

Monitor for database [databaseName] failed to start due to [username and/or password must be updated due to previous login failure; if the credentials have not changed for this database, stop the monitor, wait for the monitor to stop, then start the monitor.].

**Resolution or Workaround**

When the monitored instance is fully initialized, manually restart monitoring. On the DPA home page, click the Action drop-down menu for the instance and select Start Monitor.

**End of life**

Return to top

   

Version

EoL Announcement

EoE Effective Date

EoL Effective Date

DPA 2022.1

**January18, 2022** End-of-Life (EoL) announcement - Customers on DPA version 2022.1 or earlier should begin transitioning to the latest version of DPA.

**April18, 2023** End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version2022.1 or earlier will no longer actively be supported by SolarWinds.

**April18, 2024** End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2022.1 or earlier.

DPA 2021.3

**October 18, 2022** End-of-Life (EoL) announcement - Customers on DPA version 2021.3 or earlier should begin transitioning to the latest version of DPA.

**January 18, 2023** End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2021.3 or earlier will no longer actively be supported by SolarWinds.

**January 18, 2024** End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2021.3 or earlier.

DPA 2021.1

**October 18, 2022** End-of-Life (EoL) announcement - Customers on DPA version 2021.1 or earlier should begin transitioning to the latest version of DPA.

**January 18, 2023** End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2021.1 or earlier will no longer actively be supported by SolarWinds.

**January 18, 2024** End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2021.1 or earlier.

DPA 2020.2

**October 18, 2022** End-of-Life (EoL) announcement - Customers on DPA version 2020.2 or earlier should begin transitioning to the latest version of DPA.

**January 18, 2023** End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2020.2 or earlier will no longer actively be supported by SolarWinds.

**January 18, 2024** End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2020.2 or earlier.

**Deprecation notices**

Return to top

This version of Database Performance Analyzer deprecates the following platforms and features.

Deprecated platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features. 

 

Type

Details

DPA server OS

Installing DPA on a server with a **Windows Server 2012 R2** operating system is still supported in 2022.4, but support will be removed in an upcoming release.

_The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation_.

**Legal notices**

Return to top

© 2023 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.

CVE-2022-38112: DPA 2023.1 Release Notes

An issue was discovered in MediaWiki before 1.35.9, 1.36.x through 1.38.x before 1.38.5, and 1.39.x before 1.39.1. There is XSS in Wikibase date formatting via wikibase-time-precision-* fields. This allows JavaScript execution by staff/admin users who do not intentionally have the editsitejs capability.

**Impact:** Users with the editinterface right (not limited to editsitejs) can cause Wikibase to emit arbitrary HTML in certain situations, including in APIs where callers might treat the result as trusted HTML and use it in their own sites. On Wikidata, the editinterface right is granted not only to interface administrators (who also have editsitejs, so they can already run arbitrary JS on Wikidata, though they still shouldn’t be able to break API users in this way), but also to regular administrators as well as Wikidata staff.

**Description:** Wikibase formats time values for HTML using two classes, MwTimeIsoFormatter and HtmlTimeFormatter. MwTimeIsoFormatter is responsible for formatting the timestamp depending on the precision of the time value, using various interface messages; HtmlTimeFormatter wraps it to add the calendar model, if necessary. An example result looks like this:

14 March 1879<sup class\="wb-calendar-name"\>Gregorian</sup\>
|MwTimeIsoF…||.............HtmlTimeFormatter.............|

HtmlTimeFormatter assumes that its inner formatter (which can actually be any formatter, as far as it’s concerned) emits HTML:

/\*\*
 \* @param FormatterOptions|null $options
 \* @param ValueFormatter $dateTimeFormatter A value formatter that accepts TimeValue objects and
 \*  returns the formatted date and time, but not the calendar model. Must return HTML.
 \*/
public function \_\_construct(

HtmlTimeFormatter::format()

$formatted \= $this\->dateTimeFormatter\->format( $value );

if ( $this\->calendarNameNeeded( $value ) ) {
	$formatted .= '<sup class="wb-calendar-name">'
		. $this\->formatCalendarName( $value\->getCalendarModel() )
		. '</sup>';
}

However, MwTimeIsoFormatter returns plain text:

/\*\*
 \* @param TimeValue $timeValue
 \*
 \* @return string Text
 \*/
private function formatTimeValue( TimeValue $timeValue ) {

MwTimeIsoFormatter::getLocalizedYear()

return wfMessage(
	'wikibase-time-precision-' . ( $isBCE ? 'BCE-' : '' ) . $msg,
	$year
)
\->inLanguage( $this\->language )
\->text();

The two formatters are wired up without any escaping layer between them:

WikibaseValueFormatterBuilders::newTimeFormatter()

return new HtmlTimeFormatter( $options, new MwTimeIsoFormatter( $options ) );

So if a user with the editinterface right edits one of the relevant interface messages (wikibase-time-precision-\*) to include HTML (e.g. <script>), it will be returned unchanged by $message->text() and be added directly to the resulting HTML; this HTML can then turn up in the Wikibase UI (such as on item pages and diffs), but also in third parties who use the wbformatvalue API with the generate parameter set to one of the available HTML formats.

CVE-2023-22910: XSS in Wikibase date formatting

### Impact
The vulnerability is capable of resulting in stolen user cookies.

#### Proof of Concept
```
Login with dev account https://11.x-dev.pimcore.fun/admin/?_dc=1670962076&perspective=

Go to setting --> data objects --> classes --> events

Click media under genaral settings

Add payload in title field.

Go to data objects module and open events, xss will trigger

// PoC.js "><iMg SrC="x" oNeRRor="alert(xss);">
```
### Patches
Update to version 10.5.14 or apply this patch manually https://github.com/pimcore/pimcore/pull/13916.patch

### Workarounds
Apply https://github.com/pimcore/pimcore/pull/13916.patch manually.

### References
https://huntr.dev/bounties/129d6a4b-0504-4de1-a72c-3f12c4552343/


1.  GitHub Advisory Database
2.  GitHub Reviewed
3.  CVE-2023-0323

**pimcore is vulnerable to cross-site scripting via "title field " in data objects**

Moderate severity GitHub Reviewed Published Jan 20, 2023 in pimcore/pimcore • Updated Jan 20, 2023

Vulnerability details Dependabot alerts 0

**Package**

composer pimcore/pimcore (Composer)

**Affected versions**

< 10.5.14

**Patched versions**

10.5.14

**Description**

**Impact**

The vulnerability is capable of resulting in stolen user cookies.

**Proof of Concept**

    Login with dev account https://11.x-dev.pimcore.fun/admin/?_dc=1670962076&perspective=
    
    Go to setting --> data objects --> classes --> events
    
    Click media under genaral settings
    
    Add payload in title field.
    
    Go to data objects module and open events, xss will trigger
    
    // PoC.js "><iMg SrC="x" oNeRRor="alert(xss);">
    

**Patches**

Update to version 10.5.14 or apply this patch manually https://github.com/pimcore/pimcore/pull/13916.patch

**Workarounds**

Apply https://github.com/pimcore/pimcore/pull/13916.patch manually.

**References**

https://huntr.dev/bounties/129d6a4b-0504-4de1-a72c-3f12c4552343/

**References**

*   GHSA-6vf6-g3pr-j83h
*   https://nvd.nist.gov/vuln/detail/CVE-2023-0323
*   https://github.com/pimcore/pimcore/pull/13916.patch
*   pimcore/pimcore@746fac1
*   https://huntr.dev/bounties/129d6a4b-0504-4de1-a72c-3f12c4552343

 dvesh3 published the maintainer security advisory

Jan 16, 2023

**Severity**

Moderate

**Weaknesses**

CWE-79

**CVE ID**

CVE-2023-0323

**GHSA ID**

GHSA-6vf6-g3pr-j83h

**Source code**

pimcore/pimcore

Checking history

See something to contribute? Suggest improvements for this vulnerability.

GHSA-6vf6-g3pr-j83h: pimcore is vulnerable to cross-site scripting via "title field " in data objects

OpenText Extended ECM versions 16.2.2 through 22.3 suffer from arbitrary file deletion, information disclosure, local file inclusion, and privilege escalation vulnerabilities.

OpenText Extended ECM 22.3 File Deletion / LFI / Privilege Escsalation

Inout Multi-Vendor Shopping Cart version 3.2.3 suffers from a cross site scripting vulnerability.

    ┌┌───────────────────────────────────────────────────────────────────────────────────────┐││                                     C r a C k E r                                    ┌┘┌┘                 T H E   C R A C K   O F   E T E R N A L   M I G H T                  ││└───────────────────────────────────────────────────────────────────────────────────────┘┘ ┌────              From The Ashes and Dust Rises An Unimaginable crack....          ────┐┌┌───────────────────────────────────────────────────────────────────────────────────────┐┌┘                                      [ Exploits ]                                    ┌┘└───────────────────────────────────────────────────────────────────────────────────────┘┘:  Author   : CraCkEr                                                                    :│  Website  : inoutscripts.com                                                           ││  Vendor   : Inout Scripts - Nesote Technologies Private Limited                        ││  Software : Inout Multi-Vendor Shopping Cart 3.2.3                                     ││  Vuln Type: Reflected XSS                                                              ││  Impact   : Manipulate the content of the site                                         ││                                                                                        ││────────────────────────────────────────────────────────────────────────────────────────││                                                                                       ┌┘└───────────────────────────────────────────────────────────────────────────────────────┘┘:                                                                                        :│  Release Notes:                                                                        ││  ═════════════                                                                         ││  The attacker can send to victim a link containing a malicious URL in an email or      ││  instant message can perform a wide variety of actions, such as stealing the victim's  ││  session token or login credentials                                                    ││                                                                                        │┌┌───────────────────────────────────────────────────────────────────────────────────────┐┌┘                                                                                      ┌┘└───────────────────────────────────────────────────────────────────────────────────────┘┘Greets:    The_PitBull, Raz0r, iNs, SadsouL, His0k4, Hussin X, Mr. SQL            CryptoJob (Twitter) twitter.com/CryptozJob     ┌┌───────────────────────────────────────────────────────────────────────────────────────┐┌┘                                    © CraCkEr 2023                                    ┌┘└───────────────────────────────────────────────────────────────────────────────────────┘┘Path: /index.phpMethod: GETURL parameter 'page' is vulnerable to XSShttps://www.website.com/index.php?page=product%2fcouponsh446k%3cimg%20src%3da%20onerror%3dalert(1)%3eciqs8URL parameter 'keyword' is vulnerable to XSShttps://www.website.com/index.php?page=product/productviews&keyword=tv24708%22%3balert(1)%2f%2f279[-] Done

Tag

#xss