CVE-2023-48645
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 · uneditedAn issue was discovered in the Archibus app 4.0.3 for iOS. It uses a local database that is synchronized with a Web central server instance every time the application is opened, or when the refresh button is used. There is a SQL injection in the search work request feature in the Maintenance module of the app. This allows performing queries on the local database.
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 confidenceSQL injection vulnerability in the Archibus iOS app 4.0.3's Maintenance module search work request feature. The app uses a local SQLite database that syncs with a central Web server, and the search functionality fails to properly sanitize input, allowing arbitrary SQL queries against the local database.
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= 4.0.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Archibus iOS app installation and versionCheck the installed version of the Archibus app on the iOS device. Go to Settings > General > iPhone Storage > Archibus (or check in the App Store if installed), and confirm the version number is exactly 4.0.3.Affected if The installed version is 4.0.3 of the Archibus iOS app.
-
Confirm Maintenance module presenceOpen the Archibus iOS app and navigate through the available modules to verify the Maintenance module is installed and accessible.Affected if The Maintenance module is present and accessible within the app.
-
Locate work request search functionalityWithin the Maintenance module, locate and identify the search work request feature used to query work requests.Affected if The search work request feature exists and is accessible in the Maintenance module.
-
Verify local SQLite database usageConfirm the app is configured to use a local SQLite database that syncs with a central server. This is typically indicated by offline capability or sync status in the app settings or during normal operation.Affected if The app uses a local SQLite database for storing and syncing work request data.
A user is affected if they have Archibus iOS app version 4.0.3 with the Maintenance module installed and actively use the search work request feature against the local SQLite database.
Generated from the published advisory. Verify against your own configuration.
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 dataContact Archibus vendor for official patch; alternatively, implement parameterized queries/prepared statements in the search functionality to neutralize SQL injection vectors before any user input reaches the database layer.
- Consultation5.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,360.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-48645 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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