dbcve.org
Self Service PasswordApplication · Ltb Project

CVE-2023-49032

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 1.5.4 or later.
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
An issue in LTB Self Service Password before v.1.5.4 allows a remote attacker to execute arbitrary code and obtain sensitive information via hijack of the SMS verification code function to arbitrary phone.

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

The vulnerability in LTB Self Service Password before v1.5.4 allows hijacking of the SMS verification code function, enabling a remote attacker to send SMS messages to arbitrary phone numbers. Combined with the ability to execute arbitrary code, this creates a critical RCE and information disclosure vector.

MitigationUpgrade to version 1.5.4 or later immediately. If patching is not immediately feasible, disable or restrict access to the SMS verification function and implement additional authentication controls around SMS sending capabilities.

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
Self Service PasswordApplication
Affected:< 1.5.4

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. Identify the installed version of Self Service Password
    Check the version file or changelog typically located in the application root directory, or look for version information in the configuration files (config.inc.php or similar). Compare this version number against the affected range (< 1.5.4).
    Affected if The installed version is lower than 1.5.4 (e.g., 1.5.3, 1.5.2, 1.5.1, 1.5.0, or any version starting with 1.4.x or earlier).
  2. Locate and inspect the SMS configuration
    Find the configuration file that controls SMS settings (often in config.inc.php, config.local.php, or similar). Look for SMS-related parameters such as sms_method, sms_api_url, sms_api_key, or sms_from.
    Affected if SMS functionality is enabled in the configuration and the SMS service parameters (API keys, endpoints) are present and configurable by an attacker.
  3. Verify SMS sending capability is accessible
    Review the application web routes or source code to confirm the SMS sending endpoint exists and is accessible without proper authorization checks. Look for functions that handle SMS code generation and transmission.
    Affected if The SMS sending endpoint is exposed and does not properly validate that the request originates from legitimate password reset operations.
  4. Check for code execution capability
    Examine if the application allows configuration changes or has features that could enable arbitrary code execution (such as custom command execution, template editing, or script upload features).
    Affected if The application has additional vulnerabilities or misconfigurations that allow an attacker to execute arbitrary commands on the server.

The environment is affected if the installed LTB Self Service Password version is below 1.5.4 AND SMS verification functionality is enabled and accessible to an attacker, particularly if combined with any code execution capability.

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 1.5.4 or later
Fixed in 1.5.4
Interim mitigation

Upgrade to version 1.5.4 or later immediately. If patching is not immediately feasible, disable or restrict access to the SMS verification function and implement additional authentication controls around SMS sending capabilities.

Recommended fix High confidence

1.5.4 or later

  1. 1. Backup the current Self Service Password installation and database
  2. 2. Download version 1.5.4 or later from the official LTB Self Service Password repository (e.g., https://github.com/ltb-project/self-service-password/releases)
  3. 3. Extract the new version and replace the existing application files
  4. 4. Verify the new version is running by checking the application interface or version indicator
  5. 5. Test the SMS verification functionality to confirm the vulnerability is patched
  6. 6. Review application logs for any errors following the upgrade

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

Fix this in Self Service Password Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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