CVE-2022-1084
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 · uneditedA vulnerability classified as critical was found in SourceCodester One Church Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /one_church/userregister.php. The manipulation leads to authentication bypass. The attack can be launched remotely.
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 confidenceThe One Church Management System 1.0 contains a critical authentication bypass vulnerability in the user registration endpoint (/one_church/userregister.php). An attacker can manipulate unknown functionality within this endpoint to bypass authentication controls and gain unauthorized access to the system remotely.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify One Church Management System installationLocate the web application files on the server. Check for directories containing 'one_church' or 'church' in the name, typically found within the web server root (e.g., /var/www/html, /htdocs, or C:\inetpub\wwwroot).Affected if The software is present and running on the system.
-
Confirm the version is 1.0Review any version files, readme files, or configuration files within the One Church Management System directory for a version number. Compare the installed version against the affected range (1.0).Affected if The installed version is exactly 1.0.
-
Verify the vulnerable endpoint existsCheck for the presence of the file userregister.php within the /one_church/ subdirectory. Attempt to access this endpoint via HTTP request to confirm it responds (e.g., http://[target]/one_church/userregister.php).Affected if The file userregister.php exists and is accessible via the web.
-
Test for authentication bypassSubmit a registration request to the userregister.php endpoint with manipulated parameters, particularly focusing on unknown functionality that may allow bypassing authentication controls. Observe whether the system grants access without proper authentication validation.Affected if The endpoint allows unauthorized access or permits registration that bypasses intended authentication controls.
The system is affected if One Church Management System version 1.0 is installed and the userregister.php endpoint is accessible, as the authentication bypass vulnerability can be exploited remotely.
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 dataReview and remediate the authentication logic in userregister.php, implement proper session validation, and enforce strong authentication controls on all user registration and login flows.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1084 — 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-1084 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