CVE-2022-28078
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 · uneditedHome Owners Collection Management v1 was discovered to contain a reflected cross-site scripting (XSS) vulnerability in the Admin panel via the $_GET['page'] parameter.
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 · high confidenceReflected cross-site scripting (XSS) vulnerability in Home Owners Collection Management v1 admin panel. The $_GET['page'] parameter is not properly sanitized before being reflected in the HTML output, allowing injection of malicious JavaScript code.
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= 1.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Verify Home Owners Collection Management is installedLook for the application in your web root directory. Common paths may include /home_owners_collection or similar. Check for files like index.php, admin/login.php, or database configuration files.Affected if The application Home Owners Collection Management System is present on the server
-
Confirm the installed version is 1.0Check version information in source files, README, or any version file. Look for a version variable or constant in files like version.php, config.php, or in the admin header/footer.Affected if The installed version is exactly 1.0
-
Verify the admin panel is accessibleAttempt to access the admin login page. Common paths include /admin, /admin/login.php, or /admin/index.php. Confirm the panel loads without authentication restrictions.Affected if The admin panel endpoint is accessible and functional
-
Identify the vulnerable 'page' parameter usageExamine PHP files in the admin directory for code that handles the 'page' parameter from $_GET. Look for patterns like $_GET['page'] being directly echoed or printed into HTML without sanitization functions such as htmlspecialchars() or htmlentities().Affected if Code references $_GET['page'] and reflects it into HTML output without proper encoding
-
Test for XSS injection via the page parameterSubmit a crafted request to an admin page with a payload like ?page=<script>alert(1)</script> and observe if the script tag appears unescaped in the response HTML.Affected if The 'page' parameter value is reflected verbatim in the HTML response without encoding
Your environment is affected if Home Owners Collection Management System v1.0 is installed and the admin panel reflects the 'page' GET parameter into HTML without sanitization.
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 proper input validation and output encoding for the 'page' parameter. Use context-appropriate escaping when reflecting user input into HTML pages.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28078 — 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-2022-28078 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