LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3853: phpscriptpoint BloodBank page.php cross site scripting

A vulnerability was found in phpscriptpoint BloodBank 1.1. It has been rated as problematic. This issue affects some unknown processing of the file page.php. The manipulation leads to cross site scripting. The attack may be initiated remotely. The identifier VDB-235205 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-3853 is a cross-site scripting issue in phpscriptpoint BloodBank 1.1. It could let an attacker alter what an authenticated user sees or interacts with in the application. The supplied sources do not identify active exploitation, a vulnerable parameter, or a vendor fix.

Executive priority

Treat this as a moderate web application risk. Prioritize confirmation if BloodBank 1.1 is internet-facing or used by many semi-trusted users. The business urgency is lower than data theft or system takeover bugs, but vendor non-response increases remediation uncertainty.

Technical view

The issue is CWE-79 in unknown processing of page.php in phpscriptpoint BloodBank 1.1. The CVSS v2 score is 4.0 with AV:N/AC:L/Au:S/C:N/I:P/A:N, indicating remote reachability, low complexity, required authentication, partial integrity impact, and no stated confidentiality or availability impact.

Likely exposure

Exposure is limited to organizations running phpscriptpoint BloodBank version 1.1, especially where authenticated users from untrusted groups can access page.php. The source bundle does not specify affected parameters, deployment paths, or whether other versions are affected.

Exploitation context

The bundle says the attack may be initiated remotely, but does not show CISA KEV listing, active exploitation, public exploit evidence, or weaponized details. The vendor was reportedly contacted and did not respond.

Researcher notes

Evidence is sparse. Sources do not name the parameter, affected code path, proof-of-concept details, patch status, or impacted versions beyond BloodBank 1.1. Avoid assuming broader product impact without vendor or independent confirmation.

Mitigation direction

  • Identify whether phpscriptpoint BloodBank 1.1 is deployed.
  • Check vendor or trusted project guidance for any available fix.
  • Restrict BloodBank access to trusted users and networks where feasible.
  • Apply output encoding and input validation if maintaining local code.
  • Monitor page.php requests for suspicious or unexpected input patterns.

Validation and detection

  • Inventory deployed BloodBank versions and exposed instances.
  • Confirm whether page.php exists and is reachable to authenticated users.
  • Review page.php for reflected or stored user-controlled output.
  • Run only authorized, non-destructive XSS validation in a test environment.
  • Check logs for unusual page.php activity around authenticated sessions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-3853 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4CVSS 2.0MediumAV:N/AC:L/Au:S/C:N/I:P/A:N82.9Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

4Medium
CVSS 2.0 vector shape for CVE-2023-3853Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
phpscriptpointBloodBank1.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.