dbcve.org
LmxcmsApplication

CVE-2023-1322

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A vulnerability was found in lmxcms 1.41 and classified as critical. Affected by this issue is the function reply of the file BookAction.class.php. The manipulation of the argument id with the input 1) and updatexml(0,concat(0x7e,user()),1)# leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-222728.

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 · high confidence

SQL injection vulnerability in lmxcms 1.41's BookAction.class.php reply function allows remote attackers to inject malicious SQL via the id parameter using a time-based or error-based injection payload (e.g., updatexml). The flaw stems from unsanitized user input being directly concatenated into SQL queries.

MitigationApply input validation and convert the vulnerable SQL queries to use prepared statements/parameterized queries. If an official patch is unavailable, consider disabling the affected reply function until a fix can be implemented.

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
LmxcmsApplication
Affected:= 1.41

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm lmxcms version
    Locate the version identifier in your lmxcms installation - typically found in a version.php file, README, or in the admin dashboard under system information. Search for '1.41' or check the main index file for version strings.
    Affected if The installed version is exactly 1.41 (Lmxcms Lmxcms = 1.41)
  2. Locate BookAction.class.php
    Find the BookAction.class.php file in your lmxcms source code - it is typically located in the lib/action/ or similar directory under the application root. Use a file search or check the /lib/action/ folder.
    Affected if The file exists in the installation and contains the reply function
  3. Verify the reply function exists
    Open BookAction.class.php and locate the function named 'reply' or 'Reply' - this is the vulnerable function handling the book comment reply feature.
    Affected if The reply function is present in BookAction.class.php
  4. Check id parameter handling in SQL
    Examine the reply function code and look for SQL queries that directly use the 'id' parameter from user input without sanitization or parameterization. Look for patterns like $id being concatenated directly into SELECT, UPDATE, or DELETE statements.
    Affected if The code shows the id parameter being directly concatenated into SQL queries without prepared statements, escaping, or input validation
  5. Determine if the reply function is accessible
    Check if the book comment/reply functionality is enabled and accessible on the frontend - typically accessed via a URL path like /index.php?a=reply&m=book or similar routing depending on the lmxcms configuration.
    Affected if The reply function is publicly accessible and the book comment module is enabled

You are affected if you are running lmxcms version 1.41, the BookAction.class.php file exists with a reply function, and that function directly uses the id parameter in unsanitized SQL queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply input validation and convert the vulnerable SQL queries to use prepared statements/parameterized queries. If an official patch is unavailable, consider disabling the affected reply function until a fix can be implemented.

Fix this in Lmxcms 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 help mitigating

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-1322 — 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-1322 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