Admiror GalleryApplication · Admiror Design Studio
CVE-2023-38045
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in advcomsys.com oneVote component for Joomla. It allows XSS Targeting Non-Script Elements.
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 confidenceA stored Cross-site Scripting (XSS) vulnerability exists in the oneVote component for Joomla from advcomsys.com. The vulnerability allows injection of malicious scripts through improper input neutralization, specifically targeting non-script HTML elements (such as event handlers in attributes like onmouseover, onfocus, or style).
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
Admiror GalleryApplication
>= 5.0.0, <= 5.2.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.
-
Locate Admiror Gallery installationIdentify the Joomla extensions directory and search for files or folders named 'admiror', 'admirorgallery', or similar. Check the Joomla administrator extensions manager for installed components.Affected if Admiror Gallery extension is found in the Joomla installation
-
Determine installed versionCheck the manifest file (typically XML) within the Admiror Gallery component directory for the version attribute, or view the extension details in Joomla's extension manager.Affected if The installed version is between 5.0.0 and 5.2.0 inclusive
-
Verify oneVote component presenceSearch for the oneVote component files within the Admiror Gallery directory structure. Look for directories or files containing 'onevote', 'onevote', or 'vote' in the component path.Affected if The oneVote component directory or files exist within the Admiror Gallery installation
-
Inspect oneVote input handlingExamine the PHP files within the oneVote component for parameters that handle user-supplied data and render them in HTML attributes without sanitization. Focus on code that outputs values into attributes like style, onmouseover, or onfocus.Affected if User input is rendered directly into HTML attributes without output encoding or input validation
-
Check for existing exploitation signsReview the database tables used by oneVote for any stored malicious scripts in fields that populate non-script HTML elements. Inspect stored poll data or vote submissions for suspicious attribute-based payloads.Affected if Malicious scripts are found stored in oneVote-related database records
A user is affected if Admiror Gallery version 5.0.0 through 5.2.0 is installed with the oneVote component present and user input is rendered into HTML attributes 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 dataApply proper output encoding and input validation/sanitization to all user-supplied data rendered in the oneVote component, or update to a patched version if available from the vendor.
Fix this in Admiror Gallery
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38045 — 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-2023-38045 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