1.4

Can I use IBANs with LedgerSMB?

Submitted by ehu on Sat, 07/13/2013 - 12:53

Yes. IBANs are very long bank account numbers. LedgerSMB has no problems storing, retrieving and using these without any issue.

Read more about Can I use IBANs with LedgerSMB?
Log in or register to post comments

Is LedgerSMB SEPA proof?

Submitted by ehu on Sat, 07/13/2013 - 12:47

Yes. SEPA (Single Euro Payments Area) requires support for very long bank account numbers (IBANs or International Bank Account Numbers). LedgerSMB can store and use these numbers without problems.

Read more about Is LedgerSMB SEPA proof?
Log in or register to post comments

How do I restore my data?

Submitted by ehu on Mon, 05/13/2013 - 13:04

Assuming you have followed the How Do I Backup My Data instructions, you can restore your database as follows...

Note LedgerSMB versions prior to version 1.9.16 did not support PostgreSQL 14 or higher due to a backward incompatible change in PostgreSQL 14.

Read more about How do I restore my data?
Log in or register to post comments

How do I backup my data?

Submitted by Anonymous (not verified) on Tue, 11/29/2011 - 19:44

Log in to the the 'setup.pl' administrative interface, using your ledgersmb database admin user (usually "lsmb_dbadmin" or "postgres"). The default address for setup.pl is http://localhost/ledgersmb/setup.pl.

There are 2 buttons:

Backup database (parts, customers, accounting records, etc)
Backup roles (your login accounts and rights)

One creates a backup of the content of your database. The other creates a backup of the roles.

Read more about How do I backup my data?
1 comment
Log in or register to post comments

COGS assembly fix

Submitted by ehu on Sun, 08/18/2024 - 22:37

All versions from 1.3.0 to 1.11.16 are affected by a bug in Cost of Goods Sold (COGS) accounting for assemblies: Instead of accounting expenses and reducing inventory, negative expenses are posted, putting goods into inventory.

I never used assemblies; am I affected too?

No. Only if you used assemblies in combination with LedgerSMB 1.3.0 through 1.11.15, you're affected.

Read more about COGS assembly fix
Log in or register to post comments

cve-2024-23831 (Cross Site Request Forgery)

Submitted by ehu on Mon, 01/29/2024 - 12:51

Read more about cve-2024-23831 (Cross Site Request Forgery)

Privilege escalation through CSRF attack on 'setup.pl'

Summary

When a LedgerSMB database administrator has an active session in /setup.pl,
an attacker can trick the admin into clicking on a link which automatically
submits a request to setup.pl without the admin's consent. This request can
be used to create a new user account with full application (/login.pl)
privileges, leading to privilege escalation.

Known vulnerable

All of:

Security advisory for CVE-2021-3731 (Clickjacking)

Submitted by ehu on Fri, 08/20/2021 - 14:22

Read more about Security advisory for CVE-2021-3731 (Clickjacking)

Insufficient protection against 'clickjacking'

Summary

LedgerSMB does not sufficiently guard against being wrapped by
other sites, making it vulnerable to 'clickjacking. This allows
an attacker to trick a targetted user to execute unintended actions.

Known vulnerable

All of:

Security advisory for CVE-2021-3694 (Cross site scripting)

Submitted by ehu on Fri, 08/20/2021 - 03:13

Read more about Security advisory for CVE-2021-3694 (Cross site scripting)

Reflected cross-site scripting of authenticated users in LedgerSMB

Summary

LedgerSMB does not sufficiently HTML-encode error messages sent to the browser. By sending a specially crafted URL to an authenticated user, this flaw can be abused for remote code execution and information disclosure.

Known vulnerable

All of:

Upgrade to LedgerSMB 1.8

Submitted by ehu on Mon, 07/27/2020 - 23:11

Overview

Company database upgrades are supported all the way back from 1.4 directly to 1.8, using the 1.8 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.8 structure, while upgrades adjust the existing structure for 1.8.