CVE-2025-29267
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 · uneditedSQL Injection vulnerability in Abis, Inc Adjutant Core Accounting ERP build v.PreBeta250F allows a remote attacker to obtain a sensitive information via the cid parameter in the GET request.
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 Abis, Inc Adjutant Core Accounting ERP (build v.PreBeta250F) allows remote attackers to inject malicious SQL commands through the cid parameter in GET requests, potentially enabling unauthorized access to sensitive database information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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.
-
Identify if Adjutant Core Accounting ERP is installedLocate the installation directory or check system inventory for Abis, Inc Adjutant Core Accounting ERP softwareAffected if The product is present on the system
-
Check the installed versionLook for version information in the application (typically in About, Help, or system files) and compare to v.PreBeta250FAffected if The version is v.PreBeta250F or any version prior to patching
-
Verify web interface exposureDetermine if the ERP web interface is accessible externally or on network interfaces beyond localhostAffected if The web interface is exposed and reachable by potential attackers
-
Inspect GET request handling for the cid parameterReview application logs, proxy captures, or traffic monitoring for GET requests containing the cid parameterAffected if The cid parameter is used in GET requests without parameterized query handling
-
Check for SQL injection indicatorsExamine application and database logs for SQL syntax errors, unusual database queries, or unauthorized data access patternsAffected if SQL errors, unexpected queries, or data anomalies appear in logs after cid parameter usage
You are affected if Adjutant Core Accounting ERP v.PreBeta250F is installed and its web interface is accessible with the cid parameter handling user input in GET requests.
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 dataImplement parameterized queries (prepared statements) for all database operations involving user input, particularly the cid parameter. Additionally, apply input validation and sanitize all user-supplied data before using it in SQL queries.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29267 — 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-2025-29267 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