LiveActive security incident?Get immediate response
CVE Record

CVE-2017-6511: andrzuk/FineCMS before 2017-03-06 is vulnerable to a reflected XSS in index.php because of missing validati...

andrzuk/FineCMS before 2017-03-06 is vulnerable to a reflected XSS in index.php because of missing validation of the action parameter in application/classes/application.php.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-6511 is a reflected cross-site scripting flaw in FineCMS before 2017-03-06. A malicious link could make script run in a user's browser when that user interacts with the vulnerable site. Business impact is usually account/session risk and user trust damage, not server takeover.

Executive priority

Treat as a moderate-priority web application remediation. It is not shown as actively exploited, but public legacy CMS exposure can create user compromise risk and should be removed from the backlog if FineCMS is still deployed.

Technical view

The CVE describes missing validation of the action parameter in index.php through application/classes/application.php. It is classified as CWE-79 with CVSS 3.1 score 6.1, network-reachable, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to deployments of andrzuk/FineCMS before 2017-03-06. The source bundle does not provide CPEs, package names, or downstream product mappings, so confirm exposure by code provenance and deployed application version.

Exploitation context

The record is not marked CISA KEV, and the provided sources do not claim active exploitation. Practical exploitation would require a user to interact with a crafted FineCMS request, consistent with the CVSS user-interaction requirement.

Researcher notes

Evidence is sparse but consistent: CVE text, CVSS vector, CWE-79, GitHub issue, and fixing commit. Affected metadata in the CVE bundle is incomplete, listing vendor and product as n/a, so asset validation must rely on repository identity and code version.

Mitigation direction

  • Upgrade to FineCMS code newer than 2017-03-06 or apply the referenced fixing commit.
  • Check the project issue and commit for vendor-specific remediation details.
  • If maintaining a fork, validate and safely encode the action parameter.
  • Reduce public exposure for any legacy FineCMS instance until remediated.
  • Retire unsupported FineCMS deployments where patch status cannot be verified.

Validation and detection

  • Inventory public and internal sites using andrzuk/FineCMS.
  • Confirm whether deployed code predates the 2017-03-06 fix.
  • Review application/classes/application.php for action parameter validation changes.
  • Use a safe non-executing test value to confirm unexpected action input is rejected or encoded.
  • Check web logs for unusual action parameter values during the exposure window.
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-2017-6511 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
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2017-6511Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
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.