dbcve.org
DecalogWordPress extension · Perfops

CVE-2023-27444

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 3.7.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Pierre Lannoy / PerfOps One DecaLog plugin <= 3.7.0 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the PerfOps One DecaLog WordPress plugin (versions <= 3.7.0) allows remote attackers to trick authenticated administrators into performing unintended actions by forging malicious requests.

MitigationUpdate the DecaLog plugin to a version newer than 3.7.0 which should include proper anti-CSRF token validation; alternatively, disable the plugin until the patch can be applied.

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
DecalogWordPress extension
Affected:<= 3.7.0

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 DecaLog plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for the 'decalog' folder, or view installed plugins in the WordPress admin dashboard under Plugins > Installed Plugins
    Affected if The DecalDecaLog plugin folder exists in wp-content/plugins/ or is listed in the WordPress admin plugins page
  2. Check installed DecaLog version
    Open the main plugin file (usually decalog.php) in the decalog plugin folder and locate the 'Version' header in the plugin comment block, or check the version column in WordPress admin under Plugins > Installed Plugins
    Affected if The version displayed is 3.7.0 or any version lower than 3.7.0
  3. Confirm DecaLog plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify the DecaLog plugin shows 'Active' status rather than 'Inactive'
    Affected if The plugin is currently activated and running on the WordPress site
  4. Identify admin authentication exposure
    Review whether the WordPress site has administrator accounts with active sessions, as CSRF attacks target authenticated administrators
    Affected if Administrative users can be logged in while the vulnerable plugin version is active, allowing forged requests to be executed

A WordPress environment is affected by CVE-2023-27444 if the DecaLog plugin is installed, active, and running at version 3.7.0 or lower, exposing authenticated administrators to CSRF attacks.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.7.0
Interim mitigation

Update the DecaLog plugin to a version newer than 3.7.0 which should include proper anti-CSRF token validation; alternatively, disable the plugin until the patch can be applied.

Recommended fix Moderate confidence

3.7.1 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the DecaLog (PerfOps One) plugin
  4. 4. Check if an update is available and update to the latest version (3.7.1 or later)
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful and the plugin is now running version 3.7.1 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Decalog Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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