Is Devs Accounting safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.2.4). As of 2026-11-04. 2 issues are on record for older versions; version 1.2.1 or newer fixes all of them that state a fix. Keep Devs Accounting on the latest version (1.2.4) and remove it if you do not use it.

Which versions of Devs Accounting are vulnerable?

Known issues on record (newest first): Missing authorization check (1.2.0 and older, fixed in 1.2.1). The full list with sources is on this page.

What is the latest version of Devs Accounting?

1.2.4, according to wordpress.org (last updated 2026-07-02). It has fewer than 10 active installs.

What should I do if my Devs Accounting is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update devs-accounting). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · devs-accounting · data as of 2026-11-04

Is Devs Accounting safe? Known vulnerabilities and latest version

Latest version: 1.2.4
Last updated: 2026-07-02
Active installs: fewer than 10
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.0.8 · PHP 7.4.25+

Easily create your simple eCommerce store, get orders and also manage accounting and get automated reports. — by Devsbrain

What to do

Update to the latest version (1.2.4). Anything older than 1.2.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get devs-accounting --field=version shows what you run; wp plugin update devs-accounting updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 CVE-2026-9175 · published 2026-06-24

Missing authorization check in Devs Accounting (1.2.0 and older)

Affected: 1.2.0 and older
Fixed in: 1.2.1 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Devs Accounting – Simple Accounting and Invoicing Solution plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.2.0. This is due to the get_single_account() REST API callback being registered with a permission_callback that unconditionally returns true, providing no authentication or authorization checks on the /devs-accounting/v1/get-account/<id> endpoint. This makes it possible for unauthenticated attackers to read arbitrary private financial account records (including account name, bank name, and opening balance) by enumerating the numeric account ID, resulting in sensitive information disclosure.

NVD CVE-2026-9175 Wordfence advisory Plugin source

medium 5.3 CVE-2026-9172 · published 2026-06-24

Missing authorization check in Devs Accounting (1.2.0 and older)

Affected: 1.2.0 and older
Fixed in: 1.2.1 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Devs Accounting – Simple Accounting and Invoicing Solution plugin for WordPress is vulnerable to unauthorized modification/deletion of data due to a missing capability check on the delete_single_account() function in versions up to, and including, 1.2.0. The REST route 'devs-accounting/v1/delete-account/(?P<id>\d+)' is registered without any permission_callback, which causes WordPress to expose the endpoint to public, unauthenticated access. This makes it possible for unauthenticated attackers to soft-delete arbitrary accounting account records (wp_dac_accounts) by issuing a simple GET request to the endpoint with any account ID.

NVD CVE-2026-9172 Wordfence advisory Plugin source

Recent activity

2026-07-02 — latest release on wordpress.org (1.2.4).
2026-06-24 — Missing authorization check disclosed (CVE-2026-9175), fixed in 1.2.1.
2026-06-24 — Missing authorization check disclosed (CVE-2026-9172), fixed in 1.2.1.

Free. We check the CVE feeds every day and email you only when a new issue for Devs Accounting (devs-accounting) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/devs-accounting (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/devs-accounting"><img src="https://laskyr.com/plugins/devs-accounting/badge.svg" alt="Devs Accounting vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Devs Accounting safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (1.2.4)

What to do

Check your version

Known vulnerabilities

Missing authorization check in Devs Accounting (1.2.0 and older)

Missing authorization check in Devs Accounting (1.2.0 and older)

Recent activity

Get an email when Devs Accounting has a new vulnerability

Browse vulnerabilities

Where this data comes from