dbcve.org
WebserverApplication · Markparticle

CVE-2025-3847

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-21
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 classified as critical has been found in markparticle WebServer up to 1.0. This affects an unknown part of the file code/http/httprequest.cpp of the component Login. The manipulation of the argument username/password leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

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

SQL injection vulnerability in the login component of markparticle WebServer (up to v1.0) allows remote attackers to inject malicious SQL queries via unsanitized username/password parameters in the file code/http/httprequest.cpp.

MitigationImplement parameterized queries or prepared statements for database queries and add proper input validation on login form fields; upgrade to a patched version if available.

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
WebserverApplication
Affected:all versions

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 if markparticle WebServer is installed
    Search for markparticle WebServer files, processes, or services on the system. Common locations include /usr/local/, /opt/, or check running processes for 'markparticle' or 'webserver' entries.
    Affected if The software is found installed on the system
  2. Determine the installed version
    Check for version information in the binary, configuration files, or using version flags (e.g., --version) if available. Compare against the affected range of all versions up to 1.0.
    Affected if The installed version is 1.0 or any lower version, as all versions are affected
  3. Verify the HTTP server is running and accessible
    Check if the web server process is active and listening on network ports (commonly 80, 443, or configured ports). Use commands like netstat, ss, or curl to test connectivity.
    Affected if The HTTP server is active and network-accessible, making the login component reachable
  4. Confirm the vulnerable code file exists
    Locate the file code/http/httprequest.cpp in the WebServer installation directory or source tree. Verify it handles login requests.
    Affected if The file httprequest.cpp exists and is part of the deployed application, indicating the vulnerable code path is present
  5. Test login endpoint for SQL injection susceptibility
    If the login endpoint is accessible, observe that user input (username/password fields) is passed directly to SQL queries without apparent parameterization. This is inferred from the CVE description that input is not sanitized.
    Affected if The login component accepts user input and the code uses direct SQL query construction, confirming the vulnerability condition

If markparticle WebServer is installed and the login functionality is exposed, the environment is affected since all versions contain the SQL injection vulnerability in the login component.

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

Implement parameterized queries or prepared statements for database queries and add proper input validation on login form fields; upgrade to a patched version if available.

Fix this in Webserver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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